On Apr 9, 2014, at 1:51 AM, Riku Voipio <riku.voi...@linaro.org> wrote:
> Hi, > > The preprocessed file: > > http://people.linaro.org/~rikuvoipio/qmltextgenerator.ii.gz > > With compile command line: > > g++ -save-temps -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 > -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fvisibility=hidden > -fvisibility-inlines-hidden -Wall -W -D_REENTRANT -fPIC -o x.o > qmltextgenerator.ii > > Will take apparently forever (north of 1600min) on a debian native gcc. -O > compiles instantly. Some bisecting for gcc optimization flags later, > disabling strict aliasing allows instant build as well: > > g++ -save-temps -c -g -O2 -fno-strict-aliasing -fstack-protector > --param=ssp-buffer-size=4 -Wformat -Werror=format-security > -D_FORTIFY_SOURCE=2 -fvisibility=hidden -fvisibility-inlines-hidden -Wall -W > -D_REENTRANT -fPIC -o x.o qmltextgenerator.ii > > Happens with: > gcc version 4.8.2 (Debian 4.8.2-19) > and > gcc version 4.9.0 20140405 (experimental) [trunk revision 209146] (Debian > 20140405-1) > > Linaro binary cross-compilers are compile the file fine with -O2. > > do we do native gcc testing, or should it be just submitted upstream bugzilla? > Hi Riku, Thanks for providing preprocessed source and full command line. Ideally, you also should have provided output of "gcc -v" which shows how the compiler was configured and what various defaults are. Right now it is not clear whether the bug report is against armel, armhf or arm64. I have tested GCC in armhf Sid, armhf Trusty, arm64 Saucy, as well as recent FSF GCC mainline on armhf and can't reproduce the problem. Please attach output of "g++ -v" and the exact target / distribution configuration. Thank you, -- Maxim Kuvyrkov www.linaro.org _______________________________________________ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
