[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gcc 3.0 or bug ?

From: Nicola Pero
Subject: Re: gcc 3.0 or bug ?
Date: Fri, 4 May 2001 11:42:46 +0100 (BST)

See my previous post on the gnustep-dev mailing list - there is still a
problem with the gcc-3.x compiler, a problem which is considered to be a
plain C compiler problem - this problem crashes the 3.x compiler when
compiling the point in mframe.m where we define a nested function
returning a variable size struct, and call __builtin_return inside it.

At present, your best bet is comment out that part of code.

> Okay I took a new snapshot from base and compiled with both gcc-3.0 and
> gcc-2.95.2.
> 2.95.2 went fine, no problems at all and gcc-3.0 now gives me:
> mframe.m: In function `mframe_decode_return':
> mframe.m:1737: Internal compiler error in make_decl_rtl, at varasm.c:591
> Please submit a full bug report, with preprocessed source if appropriate.
> See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
> make[3]: *** [shared_obj/ix86/linux-gnu/gnu-gnu-gnu/mframe.o] Error 1
> make[3]: *** Waiting for unfinished jobs....
> make[2]: *** [libgnustep-base.build] Error 2
> make[1]: *** [libgnustep-base.all.library.variables] Error 2
> make[1]: Leaving directory `/opt/src/core/base/Source'
> make: *** [internal-all] Error 2

reply via email to

[Prev in Thread] Current Thread [Next in Thread]