RE: Big Problem compiling gdi tests

[Patrik Stridvall]

> I don't if it's related to me, but I got a memory problem when
> compiling the gdi tests today.
>
> I know the C code is lot bigger than any other one but I 
> think there is
> an infinite loop somewhere.According to the following report, 
> gcc tries
> to allocate 340 Mo (if succeeded, could be more...)
>
> Using RedHat 8.0 updated, gcc 3.2.7 on a Athlon 1600+
>
> make[3]: Entre dans le répertoire `/home/wine/dlls/gdi/tests'
> gcc -c -I. -I. -I../../../include -I../../../include  -g -O2 -Wall
> -mpreferred-stack-boundary=2  -fPIC -DSTRICT -DNONAMELESSUNION
> -DNONAMELESSSTRUCT  -D_REENTRANT -o generated.o generated.c
>
> cc1: Cannot allocate 188247240 bytes after allocating 15480320 bytes

Hmm. It work fine if you remove -O2.

I almost never compile Wine with optimization so I haven't detected it.

OK. I will see what I can do. It takes A LOT longer to compile with
-O2 on my computer.

Big Problem compiling gdi tests

[Sylvain Petreolle]

You're absolutely right.

I compiled ENTIRE wine with CFLAGS=-O0.

You know what ? Everything works, and it even speeds up games like
Quake III !!
> Hmm. It work fine if you remove -O2.
>
> I almost never compile Wine with optimization so I haven't detected
> it.
>
> OK. I will see what I can do. It takes A LOT longer to compile with
> -O2 on my computer.

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com