public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/38518] Excessive compile time with -O3
Date: Thu, 02 Feb 2012 19:07:00 -0000	[thread overview]
Message-ID: <bug-38518-4-dYorrHCG4d@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-38518-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2012-02-02
     Ever Confirmed|0                           |1
      Known to fail|                            |4.7.0

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-02-02 19:06:47 UTC ---
-ftime-report will report where the extra time is happening.

Anyways confirmed.
 loop unswitching        : 308.19 (70%) usr   0.05 ( 4%) sys 308.17 (70%) wall 
   105 kB ( 0%) ggc


       reply	other threads:[~2012-02-02 19:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-38518-4@http.gcc.gnu.org/bugzilla/>
2012-02-02 19:07 ` pinskia at gcc dot gnu.org [this message]
2014-01-14 11:20 ` rguenth at gcc dot gnu.org
2014-01-15 10:31 ` [Bug rtl-optimization/38518] " rguenth at gcc dot gnu.org
2014-01-15 10:37 ` rguenth at gcc dot gnu.org
2014-01-15 13:56 ` rguenth at gcc dot gnu.org
2014-01-17 10:48 ` rguenth at gcc dot gnu.org
2014-01-17 12:59 ` rguenth at gcc dot gnu.org
2021-12-25  5:11 ` [Bug middle-end/38518] " pinskia 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-38518-4-dYorrHCG4d@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).