public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/65765] [5/6 Regression] Compiling Firefox with GCC 5 leads to broken javascript engine on x86-64
Date: Wed, 15 Apr 2015 08:34:00 -0000	[thread overview]
Message-ID: <bug-65765-4-rIy9yjCIx0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65765-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65765

--- Comment #9 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
GIMPLE_PREDICT at this time is already converted to the profile (just to
explain).  If we start to do tail merging in early opts, matching gimple
predict before profile is built is probably good idea.


  parent reply	other threads:[~2015-04-15  8:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14 22:14 [Bug ipa/65765] New: " mh+gcc at glandium dot org
2015-04-15  0:52 ` [Bug ipa/65765] " mh+gcc at glandium dot org
2015-04-15  4:58 ` [Bug ipa/65765] [5/6 Regression] " trippels at gcc dot gnu.org
2015-04-15  4:58 ` trippels at gcc dot gnu.org
2015-04-15  5:41 ` trippels at gcc dot gnu.org
2015-04-15  6:55 ` jakub at gcc dot gnu.org
2015-04-15  7:04 ` mh+gcc at glandium dot org
2015-04-15  7:22 ` jakub at gcc dot gnu.org
2015-04-15  7:52 ` rguenth at gcc dot gnu.org
2015-04-15  8:33 ` hubicka at gcc dot gnu.org
2015-04-15  8:34 ` hubicka at gcc dot gnu.org [this message]
2015-04-15  8:45 ` jakub at gcc dot gnu.org
2015-04-15 11:48 ` jakub at gcc dot gnu.org
2015-04-15 12:10 ` jakub at gcc dot gnu.org
2015-04-15 12:18 ` jakub 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-65765-4-rIy9yjCIx0@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).