On Sunday, August 12, 2007 Nicolas Cannasse wrote: > Joe Wilson a écrit : >[...] >> Neko 1.6.0 compiled with gcc 4.1.1 -O[123] crashes. >> >> However, Neko compiled with gcc 4.1.1 -O[123] -fno-unit-at-a-time is okay. >> >> I don't know whether this is a bug in Neko, gcc, or libgc, but >> could you please add -fno-unit-at-a-time to the Neko Makefile? >> The gcc 4.1.1 compiler is used in many Linux distros, and it >> would be nice if it built "out of the box" on those machines.
> I'm not sure that disabling no-unit-at-a-time would be a good idea, > since it seems to improve several things : > http://lwn.net/Articles/67176/ Maybe gcc is reordering top level elements in the build and confusing the gc. http://www.gnu.org/software/gcc/gcc-4.2/changes.html says > The new command line option -fno-toplevel-reorder directs GCC to emit > top-level functions, variables, and asm statements in the same order > that they appear in the input file. This is intended to support > existing code which relies on a particular ordering (for example, code > which uses top-level asm statements to switch sections). For new code, > it is generally better to use function and variable attributes. The > -fno-toplevel-reorder option may be used for most cases which > currently use -fno-unit-at-a-time. The -fno-unit-at-a-time option will > be removed in some future version of GCC. If you know of a case which > requires -fno-unit-at-a-time which is not fixed by > -fno-toplevel-reorder, please open a bug report. e -- Doug Currie Londonderry, NH, USA -- Neko : One VM to run them all (http://nekovm.org)
