public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/44618] [4.4/4.5/4.6/4.7 regression] wrong code with -frename-registers
Date: Wed, 27 Apr 2011 10:16:00 -0000	[thread overview]
Message-ID: <bug-44618-4-HAEOiKEq0Q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-44618-4@http.gcc.gnu.org/bugzilla/>

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

Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dje at gcc dot gnu.org

--- Comment #19 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2011-04-27 09:35:44 UTC ---
Yes, the problem is in the PowerPC back-end.  And I also think that the use
trick is the way to go.  The mildly annoying thing is the need to duplicate
patterns just because of the different register number, but I'm not sure this
can be avoided.  In any case, this is up to the PowerPC maintainer at this
point.


  parent reply	other threads:[~2011-04-27 10:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-44618-4@http.gcc.gnu.org/bugzilla/>
2011-04-27  9:29 ` ebotcazou at gcc dot gnu.org
2011-04-27 10:16 ` ebotcazou at gcc dot gnu.org [this message]
2011-04-27 10:21 ` [Bug target/44618] Arguments are not passed correctly to out-of-line restore functions ebotcazou at gcc dot gnu.org
2011-05-19 13:00 ` [Bug target/44618] [4.4/4.5/4.6/4.7 regression] wrong code with -frename-registers jakub at gcc dot gnu.org
2011-05-19 16:18 ` edmar at freescale dot com
2011-05-23 22:13 ` edmar at freescale dot com
2011-05-23 22:36 ` edmar at freescale dot com
2011-06-02 15:35 ` edmar at freescale dot com
2011-06-12 12:47 ` rguenth at gcc dot gnu.org
2011-06-15 16:45 ` [Bug target/44618] [4.4/4.5/4.6 " jakub at gcc dot gnu.org
2011-06-16  7:50 ` jakub at gcc dot gnu.org
2011-06-16  7:54 ` jakub at gcc dot gnu.org
2011-08-24  6:13 ` [Bug target/44618] [4.4/4.5 " galak at kernel dot crashing.org
2011-08-24 15:09 ` edmar at freescale dot com
2012-02-17 11:11 ` bernhard.kaindl at thalesgroup dot com
2012-03-13 14:45 ` [Bug target/44618] [4.5 " jakub at gcc dot gnu.org
2012-07-02  9:41 ` 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-44618-4-HAEOiKEq0Q@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).