public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/58479] [4.9 Regression] slow compilation on x86_64-linux at -O1 (and above) with -g, but checking disabled
Date: Thu, 19 Sep 2013 20:06:00 -0000	[thread overview]
Message-ID: <bug-58479-4-2KbZnVDUvj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58479-4@http.gcc.gnu.org/bugzilla/>

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

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|slow compilation on         |[4.9 Regression] slow
                   |x86_64-linux at -O1 (and    |compilation on x86_64-linux
                   |above) with -g, but         |at -O1 (and above) with -g,
                   |checking disabled           |but checking disabled

--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
With 4.8/4.7 it's indeed not that bad, thus tentatively marking as 4.9
regression...


  parent reply	other threads:[~2013-09-19 20:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-19 19:47 [Bug middle-end/58479] New: " su at cs dot ucdavis.edu
2013-09-19 20:03 ` [Bug middle-end/58479] " mpolacek at gcc dot gnu.org
2013-09-19 20:06 ` mpolacek at gcc dot gnu.org [this message]
2013-09-19 20:10 ` [Bug middle-end/58479] [4.9 Regression] " mpolacek at gcc dot gnu.org
2014-01-20  9:56 ` [Bug middle-end/58479] [4.9 Regression] slow var-tracking " rguenth at gcc dot gnu.org
2014-01-20 10:48 ` jakub at gcc dot gnu.org
2014-03-03 14:01 ` jakub at gcc dot gnu.org
2014-03-12 15:28 ` [Bug middle-end/58479] [4.8/4.9 " jakub at gcc dot gnu.org
2014-04-22 11:37 ` [Bug middle-end/58479] [4.8/4.9/4.10 " jakub at gcc dot gnu.org
2014-07-16 13:31 ` jakub at gcc dot gnu.org
2014-10-30 10:42 ` [Bug middle-end/58479] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-06-26 20:10 ` [Bug middle-end/58479] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:36 ` jakub at gcc dot gnu.org
2021-05-14  9:46 ` [Bug middle-end/58479] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:06 ` rguenth at gcc dot gnu.org
2022-05-27  9:34 ` [Bug debug/58479] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:30 ` jakub at gcc dot gnu.org
2023-07-07 10:30 ` [Bug debug/58479] [11/12/13/14 " rguenth at gcc dot gnu.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-58479-4-2KbZnVDUvj@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).