Mail Archives: djgpp/2005/02/24/02:20:29
| X-Authentication-Warning: | delorie.com: mail set sender to djgpp-bounces using -f
|
| From: | Sterten AT aol DOT com
|
| Message-ID: | <14.3fb9cae4.2f4ed770@aol.com>
|
| Date: | Thu, 24 Feb 2005 02:08:32 EST
|
| Subject: | Re: files > 4GB There is always a solution
|
| To: | djgpp AT delorie DOT com
|
| MIME-Version: | 1.0
|
| X-Mailer: | 9.0 SE for Windows sub 5003
|
| Reply-To: | djgpp AT delorie DOT com
|
-------------------------------1109228912
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
I can already generate files larger then 4GB, just not open them.
I'd thought, thet gcc maybe tries to determine the filelength on opening
and stores it for possible later access - and that's where it fails.
But I don't need that. The file is just read sequentially.
From DOS-programming, I remember there were some interrupts with parameters.
Isn't it similar with NTFS ?
Shouldn't it be possible to just change some parameters to handle big files
correctly ? Why is it so difficult ?
You might think, 4GB is rather big and noone needs it anyway,
but Billy Gates also once said, nobody would ever need more than
1 MB of RAM ...
Well, with the new 64-bit processors it's quite natural to address the bytes
in a file >4GB. Will we be able to use 64-bit variables with gcc/djgpp
or will this never be supported ?
-------------------------------1109228912
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DUS-ASCII">
<META content=3D"MSHTML 6.00.2800.1141" name=3DGENERATOR></HEAD>
<BODY id=3Drole_body style=3D"FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY:=20=
Arial"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Drol=
e_document=20
face=3DArial color=3D#000000 size=3D2><FONT id=3Drole_document face=3DArial=20=
color=3D#000000=20
size=3D2>
<DIV> </DIV>
<DIV>I can already generate files larger then 4GB, just not open them.</DIV>
<DIV>I'd thought, thet gcc maybe tries to determine the filelength on=20
opening</DIV>
<DIV>and stores it for possible later access - and that's where it fails.</D=
IV>
<DIV>But I don't need that. The file is just read sequentially.</DIV>
<DIV> </DIV>
<DIV>From DOS-programming, I remember there were some interrupts with=20
parameters.</DIV>
<DIV>Isn't it similar with NTFS ?</DIV>
<DIV>Shouldn't it be possible to just change some parameters to handle big=20
files</DIV>
<DIV>correctly ? Why is it so difficult ?</DIV>
<DIV> </DIV>
<DIV>You might think, 4GB is rather big and noone needs it anyway,</DIV>
<DIV>but Billy Gates also once said, nobody would ever need more than</DIV>
<DIV>1 MB of RAM ...</DIV>
<DIV> </DIV>
<DIV>Well, with the new 64-bit processors it's quite natural to address the=20
bytes</DIV>
<DIV>in a file >4GB. Will we be able to use 64-bit variables with=20
gcc/djgpp</DIV>
<DIV>or will this never be supported ?</DIV></FONT></FONT></BODY></HTML>
-------------------------------1109228912--
- Raw text -