public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/27075] [4.1/4.2 Regression] Compiler generate incorrect assembler for __sync_fetch-* builtins on e500 aka SPE
Date: Thu, 17 Aug 2006 20:29:00 -0000	[thread overview]
Message-ID: <20060817202908.16280.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27075-12262@http.gcc.gnu.org/bugzilla/>



------- Comment #16 from mmitchel at gcc dot gnu dot org  2006-08-17 20:29 -------
I think the patch in Comment #8 is OK, but that the right approach would be to
stop using %y to denote two different things.  I think we should add
documentation saying that %y has dual meanings and check in this patch.  Then,
as a separate issue, I think we should split %y into two different operand
letters so that each has consitent semantics.

I've CC'd the PowerPC maintainers on this PR.  If neither of them object within
24 hours, please check in this patch.

Thanks,

-- Mark


-- 

mmitchel at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dje at watson dot ibm dot
                   |                            |com, geoffk at apple dot
                   |                            |com, joseph at codesourcery
                   |                            |dot com


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


  parent reply	other threads:[~2006-08-17 20:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-07 15:29 [Bug c/27075] New: Compiler generate incorrect assembler edmar at freescale dot com
2006-04-07 15:32 ` [Bug c/27075] " edmar at freescale dot com
2006-04-07 15:33 ` [Bug target/27075] " pinskia at gcc dot gnu dot org
2006-04-07 15:45 ` edmar at freescale dot com
2006-04-07 15:48 ` pinskia at gcc dot gnu dot org
2006-04-07 15:53 ` pinskia at gcc dot gnu dot org
2006-04-07 15:54 ` edmar at freescale dot com
2006-04-07 16:00 ` [Bug target/27075] [4.1 Regression] Compiler generate incorrect assembler for __sync_fetch-* builtins on e500 aka SPE pinskia at gcc dot gnu dot org
2006-04-09 13:51 ` [Bug target/27075] [4.1/4.2 " amodra at bigpond dot net dot au
2006-04-16 19:19 ` mmitchel at gcc dot gnu dot org
2006-04-17 15:57 ` edmar at freescale dot com
2006-05-25  2:47 ` mmitchel at gcc dot gnu dot org
2006-07-22 21:12 ` echristo at apple dot com
2006-07-22 22:16 ` pinskia at gcc dot gnu dot org
2006-07-24 15:05 ` edmar at freescale dot com
2006-07-24 19:34 ` raj dot khem at gmail dot com
2006-07-26 12:53 ` dtemirbulatov at gmail dot com
2006-08-17 20:29 ` mmitchel at gcc dot gnu dot org [this message]
2006-08-25 14:36 ` drow at gcc dot gnu dot org
2006-08-25 14:37 ` drow at gcc dot gnu dot org
2006-08-25 18:56 ` dje at gcc dot gnu dot org
2006-08-25 18:57 ` dje at gcc dot gnu dot org
2006-08-25 19:07 ` dje at gcc dot gnu dot 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=20060817202908.16280.qmail@sourceware.org \
    --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).