public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/53199] __builtin_bswap64 and __builtin_bswap32 generate errors if -mcpu=power6 Date: Thu, 03 May 2012 21:48:00 -0000 [thread overview] Message-ID: <bug-53199-4-GGGh3BbGJ0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53199-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53199 --- Comment #2 from Michael Meissner <meissner at gcc dot gnu.org> 2012-05-03 21:47:49 UTC --- Author: meissner Date: Thu May 3 21:47:45 2012 New Revision: 187119 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=187119 Log: [gcc] 2012-05-03 Michael Meissner <meissner@linux.vnet.ibm.com> PR target/53199 * config/rs6000/rs6000.md (bswapdi splitters): If -mavoid-indexed-addresses (or -mcpu=power6 which sets it by default) is used, generate an alternate sequence that does not depend on using indexed addressing. [gcc/testsuite] 2012-05-03 Michael Meissner <meissner@linux.vnet.ibm.com> PR target/53199 * gcc.target/powwerpc/pr53199.c: New file. Added: trunk/gcc/testsuite/gcc.target/powerpc/pr53199.c Modified: trunk/gcc/ChangeLog trunk/gcc/config/rs6000/rs6000.md trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2012-05-03 21:48 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-02 19:08 [Bug target/53199] New: " meissner at gcc dot gnu.org 2012-05-02 19:16 ` [Bug target/53199] " meissner at gcc dot gnu.org 2012-05-03 21:48 ` meissner at gcc dot gnu.org [this message] 2012-05-04 0:28 ` meissner at gcc dot gnu.org 2012-05-04 0:32 ` meissner at gcc dot gnu.org 2012-05-04 1:07 ` meissner at gcc dot gnu.org 2012-05-04 1:46 ` meissner at gcc dot gnu.org 2014-12-05 17:51 ` meissner 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-53199-4-GGGh3BbGJ0@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: linkBe 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).