------- Additional Comments From pinskia at gcc dot gnu dot org 2005-08-20
02:26 -------
earth:~>time gcc -O1 t.cc -S
5.993u 0.056s 0:06.18 97.7% 0+0k 0+0io 0pf+0w
earth:~>time gcc -O1 t.cc -S -O2
11.529u 0.058s 0:11.84 97.7% 0+0k 0+0io 0pf+0w
earth:~>time gcc t.cc -S
0.426u 0.012s 0:00.93 46.2% 0+0k 0+0io 0pf+0w
This is without checking disable.
Interesting 2.95.3 does not have the issue even with -fstrict-aliasing:
earth:~>time ~/ia32_linux_gcc2_95/bin/gcc t.cc -S
0.248u 0.019s 0:00.51 49.0% 0+0k 0+0io 0pf+0w
earth:~>time ~/ia32_linux_gcc2_95/bin/gcc t.cc -S -O1
1.259u 0.013s 0:01.63 77.3% 0+0k 0+0io 0pf+0w
earth:~>time ~/ia32_linux_gcc2_95/bin/gcc t.cc -S -O2
1.630u 0.021s 0:01.90 86.8% 0+0k 0+0io 0pf+0w
earth:~>time ~/ia32_linux_gcc2_95/bin/gcc t.cc -S -O2 -fstrict-aliasing
1.626u 0.018s 0:01.81 90.0% 0+0k 0+0io 0pf+0w
This has been a bug since 3.0.4.
It also happens on x86 too.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
GCC build triplet|alphaev68-unknown-linux-gnu |
GCC host triplet|alphaev68-unknown-linux-gnu |
GCC target triplet|alphaev68-unknown-linux-gnu |
Known to fail| |3.0.4 3.3.3 3.4.0 4.0.0
Known to work| |2.95.3
Last reconfirmed|0000-00-00 00:00:00 |2005-08-20 02:26:31
date| |
Summary|Long compile time for array |[3.4/4.0/4.1 Regression]
|initializer with inlined |Long compile time for array
|constructor |initializer with inlined
| |constructor
Target Milestone|--- |4.0.2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23490
