public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/27733]  New: Large compile time regression
Date: Mon, 22 May 2006 20:37:00 -0000	[thread overview]
Message-ID: <bug-27733-276@http.gcc.gnu.org/bugzilla/> (raw)

Relative to gcc version 4.0.4 20060507 (prerelease) (Debian 4.0.3-3),
gcc version 4.1.1 20060511 (prerelease) (Debian 4.1.0-4) and also my own
build of 4.2 exhibit a large increase in compile on the attached file.
On my c3k, the time goes from ~ 5 seconds to 49 minutes.

The compile command used is:

/usr/bin/hppa64-linux-gnu-gcc-4.1 -nostdinc -v alloc.i -mno-space-regs
-mfast-indirect-calls -mdisable-fpregs -march=2.0 -mschedule=8000 -O2 -Wall
-Wundef -Wstrict-prototypes -Wno-trigraphs -Wdeclaration-after-statement
-Wno-pointer-sign -fno-strict-aliasing -fno-common -fomit-frame-pointer
-ffunction-sections -S


-- 
           Summary: Large compile time regression
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: danglin at gcc dot gnu dot org
 GCC build triplet: hppa-unknown-linux-gnu
  GCC host triplet: hppa-unknown-linux-gnu
GCC target triplet: hppa64-unknown-linux-gnu


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


             reply	other threads:[~2006-05-22 20:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-22 20:37 danglin at gcc dot gnu dot org [this message]
2006-05-22 20:38 ` [Bug middle-end/27733] " danglin at gcc dot gnu dot org
2006-05-22 22:26 ` danglin at gcc dot gnu dot org
2006-05-23  2:30 ` [Bug middle-end/27733] [4.1/4.2 Regression] " pinskia at gcc dot gnu dot org
2006-05-23 13:50 ` dave at hiauly1 dot hia dot nrc dot ca
2006-05-25  2:42 ` mmitchel at gcc dot gnu dot org
2006-06-04 19:22 ` mmitchel at gcc dot gnu dot org
2006-06-06 20:08 ` sje at cup dot hp dot com
2006-06-06 20:48 ` sje at cup dot hp dot com
2006-06-06 21:05 ` falk at debian dot org
2006-06-06 21:32 ` sje at cup dot hp dot com
2006-06-08 12:24 ` bonzini at gnu dot org
2006-06-08 12:27 ` bonzini at gnu dot org
2006-06-08 13:04 ` bonzini at gnu dot org
2006-06-08 15:24 ` sje at cup dot hp dot com
2006-06-08 15:39 ` bonzini at gnu dot org
2006-06-08 15:50 ` bonzini at gcc dot gnu dot org
2006-06-08 16:38 ` sje at cup dot hp dot com
2006-06-11 15:43 ` [Bug middle-end/27733] [4.1 " soete dot joel at tiscali dot be
2006-06-13 13:06 ` bonzini at gcc dot gnu dot org
2006-06-13 13:12 ` bonzini at gnu dot org
2006-06-13 16:30 ` soete dot joel at tiscali dot be

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-27733-276@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).