public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/63566] [5 Regression] i686 bootstrap fails: ICE RTL flag check: INSN_UID used with unexpected rtx code 'set' in INSN_UID, at rtl.h:1326
Date: Mon, 09 Feb 2015 08:14:00 -0000	[thread overview]
Message-ID: <bug-63566-4-X7eqm7S54M@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63566-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Even with all the committed patches I don't see any change on the #c5 testcase,
which in 4.9 used regparm(3) calling convention e.g. for f1 and f2, but with
current trunk still uses regparm(0).


  parent reply	other threads:[~2015-02-09  8:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16 22:17 [Bug ipa/63566] New: " mliska at suse dot cz
2014-10-16 22:22 ` [Bug ipa/63566] " mliska at suse dot cz
2014-10-17  9:41 ` trippels at gcc dot gnu.org
2014-11-18 14:57 ` jakub at gcc dot gnu.org
2014-11-20 12:26 ` rguenth at gcc dot gnu.org
2015-01-26 15:05 ` jakub at gcc dot gnu.org
2015-02-02 18:07 ` hubicka at gcc dot gnu.org
2015-02-08 20:09 ` hubicka at gcc dot gnu.org
2015-02-08 20:13 ` hubicka at gcc dot gnu.org
2015-02-08 21:05 ` hubicka at gcc dot gnu.org
2015-02-08 21:09 ` hubicka at gcc dot gnu.org
2015-02-09  8:14 ` jakub at gcc dot gnu.org [this message]
2015-02-09 20:45 ` hubicka at gcc dot gnu.org
2015-02-09 20:48 ` hubicka at gcc dot gnu.org
2015-02-09 21:58 ` 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-63566-4-X7eqm7S54M@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).