public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug pending/39657]  New: [4.3 Regression] compiling ruby (yacc) output takes inordinate amount of time on x86 with -O2
Date: Mon, 06 Apr 2009 00:48:00 -0000	[thread overview]
Message-ID: <bug-39657-10160@http.gcc.gnu.org/bugzilla/> (raw)

gcc 4.1, 4.2, and 4.4 all take less than 30 seconds to compile this file.  but
gcc-4.3 can easily take more like 5 minutes.

the file comes from the preprocessed output of a file in the ruby package.


-- 
           Summary: [4.3 Regression] compiling ruby (yacc) output takes
                    inordinate amount of time on x86 with -O2
           Product: gcc
           Version: 4.3.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: pending
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: vapier at gentoo dot org
GCC target triplet: i686-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39657


             reply	other threads:[~2009-04-06  0:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06  0:48 vapier at gentoo dot org [this message]
2009-04-06  0:50 ` [Bug pending/39657] " vapier at gentoo dot org
2009-04-06  9:39 ` [Bug tree-optimization/39657] " rguenth at gcc dot gnu dot org
2009-04-22 13:31 ` [Bug tree-optimization/39657] [4.3 Regression] compiling ruby (yacc) output takes inordinate amount of time with PRE and large SCCs rguenth at gcc dot gnu dot org
2009-08-04 12:48 ` rguenth at gcc dot gnu dot org
2010-04-27 11:18 ` 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-39657-10160@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: link
Be 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).