public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "edwintorok at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/37658] New: gcc-4.3 regression: long compile times on source with lots of labels/gotos Date: Sat, 27 Sep 2008 16:21:00 -0000 [thread overview] Message-ID: <bug-37658-15165@http.gcc.gnu.org/bugzilla/> (raw) Using gcc-4.3 to compile Gauche-0.8.13/src/vm.c with -O2 takes several minutes, this problem doesn't occur with gcc-4.2. $ time /usr/bin/gcc-4.3 -O2 vm.i -c real 2m13.341s user 2m13.008s sys 0m0.308s $ time /usr/bin/gcc-4.3 -O2 testcase.i -c real 2m2.527s user 2m2.004s sys 0m0.336s $ time /usr/bin/gcc-4.2 -O2 vm.i -c real 0m2.265s user 0m2.216s sys 0m0.040s $ gcc-4.3 -v Using built-in specs. Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.2-1' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-cld --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.3.2 (Debian 4.3.2-1) $ gcc-4.2 -v Using built-in specs. Target: x86_64-linux-gnu Configured with: ../src/configure -v --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.2 --program-suffix=-4.2 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.2.4 (Debian 4.2.4-3) [not sure about the component, it could be the register allocator, because I encountered a spiller error while reducing the testcase] -- Summary: gcc-4.3 regression: long compile times on source with lots of labels/gotos Product: gcc Version: 4.3.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: edwintorok at gmail dot com GCC build triplet: x86_64-linux-gnu GCC host triplet: x86_64-linux-gnu GCC target triplet: x86_64-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37658
next reply other threads:[~2008-09-27 16:21 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-09-27 16:21 edwintorok at gmail dot com [this message] 2008-09-27 16:22 ` [Bug tree-optimization/37658] " edwintorok at gmail dot com 2008-09-28 19:38 ` [Bug tree-optimization/37658] [4.3 Regression] " pinskia at gcc dot gnu dot org 2008-09-28 19:43 ` [Bug tree-optimization/37658] [4.3 Regression] long compile times in PRE " pinskia at gcc dot gnu dot org 2008-10-01 21:34 ` rguenth at gcc dot gnu dot org 2008-10-10 9:16 ` rguenth at gcc dot gnu dot org 2009-01-24 10:26 ` rguenth at gcc dot gnu dot org 2009-08-04 12:43 ` rguenth at gcc dot gnu dot org 2010-05-22 18:31 ` rguenth at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-37658-15165@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).