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?
Riku
On Apr 9, 2014, at 1:51 AM, Riku Voipio riku.voipio@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
On 9 April 2014 22:22, Maxim Kuvyrkov maxim.kuvyrkov@linaro.org wrote:
On Apr 9, 2014, at 1:51 AM, Riku Voipio riku.voipio@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
Hi,
This is with debian/armel.
g++ -v Using built-in specs. COLLECT_GCC=g++ COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabi/4.8/lto-wrapper Target: arm-linux-gnueabi Configured with: ../src/configure -v --with-pkgversion='Debian 4.8.2-19' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.8 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libmudflap --disable-libitm --disable-libquadmath --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-armel/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-armel --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-armel --with-arch-directory=arm --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-sjlj-exceptions --with-arch=armv4t --with-float=soft --enable-checking=release --build=arm-linux-gnueabi --host=arm-linux-gnueabi --target=arm-linux-gnueabi Thread model: posix gcc version 4.8.2 (Debian 4.8.2-19)
Riku
Hi Riku,
I can reproduce this with recent FSF mainline configured similarly to Debian's arm-linux-gnueabi soft-float target. It doesn't reproduce on hard-float.
We are looking into this.
Thanks for the bug report!
-- Maxim Kuvyrkov www.linaro.org
On Apr 11, 2014, at 1:55 AM, Riku Voipio riku.voipio@linaro.org wrote:
On 9 April 2014 22:22, Maxim Kuvyrkov maxim.kuvyrkov@linaro.org wrote: On Apr 9, 2014, at 1:51 AM, Riku Voipio riku.voipio@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
Hi,
This is with debian/armel.
g++ -v Using built-in specs. COLLECT_GCC=g++ COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabi/4.8/lto-wrapper Target: arm-linux-gnueabi Configured with: ../src/configure -v --with-pkgversion='Debian 4.8.2-19' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.8 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libmudflap --disable-libitm --disable-libquadmath --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-armel/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-armel --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-armel --with-arch-directory=arm --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-sjlj-exceptions --with-arch=armv4t --with-float=soft --enable-checking=release --build=arm-linux-gnueabi --host=arm-linux-gnueabi --target=arm-linux-gnueabi Thread model: posix gcc version 4.8.2 (Debian 4.8.2-19)
Riku
linaro-toolchain@lists.linaro.org
-
Maxim Kuvyrkov -
Riku Voipio