[Bug c/48913] gcc -flto hangs and allocates all memory

2011-05-09 Thread sdack at gmx dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48913 Sven C. Dack changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|

[Bug c/48913] gcc -flto hangs and allocates all memory

2011-05-06 Thread sdack at gmx dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48913 --- Comment #2 from Sven C. Dack 2011-05-06 12:35:57 UTC --- I understand that it can use a lot of memory, but does LTO not partition the work load and thus keep the memory consumption under control? Whatever the default behaviour of LTO here is,

[Bug c/48913] New: gcc -flto hangs and allocates all memory

2011-05-06 Thread sdack at gmx dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48913 Summary: gcc -flto hangs and allocates all memory Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassig...@gc

[Bug bootstrap/30853] warnings about traditional.c during bootstrap with -O3, leading to internal error

2007-02-23 Thread sdack at gmx dot de
--- Comment #4 from sdack at gmx dot de 2007-02-23 15:52 --- Subject: Re: warnings about traditional.c during bootstrap with -O3, leading to internal error > > Still, I find it a bit scary installing gcc without first > bootstrapping it. I > > trust the result more

[Bug bootstrap/30853] warnings about traditional.c during bootstrap with -O3, leading to internal error

2007-02-23 Thread sdack at gmx dot de
--- Comment #2 from sdack at gmx dot de 2007-02-23 13:03 --- Subject: Re: warnings about traditional.c during bootstrap with -O3, leading to internal error > --enable-bootstrap > > Don't use that option for 4.1.x. > > Can you try again without that option?

[Bug bootstrap/30853] New: warnings about traditional.c during bootstrap with -O3, leading to internal error

2007-02-18 Thread sdack at gmx dot de
not defined -- Summary: warnings about traditional.c during bootstrap with -O3, leading to internal error Product: gcc Version: 4.1.2 Status: UNCONFIRMED Severity: minor Priority: P3 Component: bootstrap AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: sdack at gmx dot de GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30853

[Bug bootstrap/30810] top-level BOOT_CFLAGS not being used for bootstrapping

2007-02-18 Thread sdack at gmx dot de
--- Comment #7 from sdack at gmx dot de 2007-02-18 22:12 --- I dug a bit deeper and should now get my gcc compiled with a load full of options. It is compiling right now. The idea is to get a highly optimized output as well as to cause high stress to gcc. However, there is a file called

[Bug bootstrap/30810] top-level BOOT_CFLAGS not being used for bootstrapping

2007-02-16 Thread sdack at gmx dot de
--- Comment #5 from sdack at gmx dot de 2007-02-16 19:03 --- What I now did was the following: I set CFLAGS, CXXFLAGS, LIBCFLAGS, LIBCXXFLAGS and BOOT_CFLAGS on the command line to make to: "-pipe -march=athlon-xp -msse -mmmx -m3dnow -mfpmath=sse -O3 -mpreferred-stack-bound

[Bug bootstrap/30810] top-level BOOT_CFLAGS not being used for bootstrapping

2007-02-16 Thread sdack at gmx dot de
--- Comment #4 from sdack at gmx dot de 2007-02-16 13:18 --- Subject: Re: top-level BOOT_CFLAGS not being used for bootstrapping pinskia at gcc dot gnu dot org schrieb: > --- Comment #2 from pinskia at gcc dot gnu dot org 2007-02-16 01:48 > --- >> I believe th

[Bug bootstrap/30810] top-level BOOT_CFLAGS not being used for bootstrapping

2007-02-16 Thread sdack at gmx dot de
--- Comment #3 from sdack at gmx dot de 2007-02-16 13:17 --- Subject: Re: top-level BOOT_CFLAGS not being used for bootstrapping pinskia at gcc dot gnu dot org schrieb: > --- Comment #1 from pinskia at gcc dot gnu dot org 2007-02-15 21:28 > --- > You mentioned BOOT

[Bug bootstrap/30810] New: top-level BOOT_CFLAGS not being used for bootstrapping

2007-02-15 Thread sdack at gmx dot de
y: P3 Component: bootstrap AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: sdack at gmx dot de GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30810