public inbox for firstname.lastname@example.org
help / color / mirror / Atom feed
* Re: middle-end/10776: [3.3/3.4 regression] Large aggregate initializers with a single relocated entry causes excessive compile time regression
@ 2003-05-15 0:00 giovannibajo
0 siblings, 0 replies; only message in thread
From: giovannibajo @ 2003-05-15 0:00 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, giovannibajo, gonz, nobody
Old Synopsis: [3.3 regression] Large aggregate initializers cause GCC to fail
New Synopsis: [3.3/3.4 regression] Large aggregate initializers with a single relocated entry causes excessive compile time regression
State-Changed-When: Thu May 15 00:00:00 2003
I have attached the reduced testcase as "pr10776.cpp.bz2".
There is a huge compile time regression when the code is
being compiled with -O, in 3.3 and 3.4 (and 3.2).
The same code compiles in a decent amount of time (and
memory usage) with 2.95. Notice that the whole regression
can be eliminated by commenting a single relocated entry
in the initializers (in the code, just comment the macro
COMPILE_TIME_BUG defined at the beginning of the file).
It looks like the optimizer is dieing because too much
code is generated in the constructor/destructor initializer
function. I think this is a middle-end bug, and I moved it
to the middle-end category: probably GCC should be smarter
and use memcpy whenever it's possible.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-05-15 0:00 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-05-15 0:00 middle-end/10776: [3.3/3.4 regression] Large aggregate initializers with a single relocated entry causes excessive compile time regression giovannibajo
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).