Mail Archives: djgpp/1998/06/21/16:26:27
Kertis A. Henderson wrote:
>
> Hello. I recently installed the latest DOSEmu for linux, and the first
> this that I installed was djgpp (or course).
What do you consider the "latest"? I believe they have both "stable"
and "development" versions. The latest stable (I think) is 0.66.7,
while development should be around 0.99.x
> Well, I tried to compile
> Allegro (the May 25th WIP), and I could only compile about 50% of the .o
> files. For the rest, I was getting a message saying that I ran out of
> virtual memory. I then changed the flags in the makefile from -O3 to
> -O2, and I could compile about 90% of the .o files, still getting this
> error on a few compiles. I then increased my DPMI memory from 8MB to
> 16MB. I can now compile the entile Allegro library with -O3.
>
> Well, I was not aware that gcc would use this much memory. What I'd
> like to know, is why did some of the code run fine with 8MB and -O3, and
> some with -O2? Does optimization use THAT much memory? Or, is this a
> problem with DOSEmu?
GCC does use an awful lot of memory. -O3 is a special culprit; it
enables inlining of all functions. This means (I think) that the
internal RTL representation of every function is stored in memory for
the rest of the compile, and that could take a whole lot. The `-dm'
option to GCC will print an approximation of how much memory the
compiler is using for data.
> Also, has anyone else run Allegro programs under X-windows? When I run
> test.exe, I get the video mode selection screen, but as soon as I move
> the mouse far enough to change the dialog's focus, I get a SIGSEGV.
> Does anyone have any experience with this?
I use 0.66.7, and for me the mouse doesn't work correctly at all. It
might be time to upgrade...
Also, I expect that any program that tries to use the timer won't work.
--
Nate Eldredge
nate AT cartsys DOT com
- Raw text -