public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/53568] SH Target: Add support for bswap built-ins Date: Wed, 13 Jun 2012 18:46:00 -0000 [thread overview] Message-ID: <bug-53568-4-9zAbuy3BwE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53568-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53568 --- Comment #1 from Oleg Endo <olegendo at gcc dot gnu.org> 2012-06-13 18:45:56 UTC --- Author: olegendo Date: Wed Jun 13 18:45:17 2012 New Revision: 188524 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=188524 Log: PR target/53568 * config/sh/sh.md (bswapsi2): New expander. (swapbsi2): New insn. Modified: trunk/gcc/ChangeLog trunk/gcc/config/sh/sh.md
next prev parent reply other threads:[~2012-06-13 18:46 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-03 20:03 [Bug target/53568] New: " olegendo at gcc dot gnu.org 2012-06-11 20:18 ` [Bug target/53568] " olegendo at gcc dot gnu.org 2012-06-13 18:46 ` olegendo at gcc dot gnu.org [this message] 2012-06-14 19:33 ` olegendo at gcc dot gnu.org 2012-07-02 23:00 ` olegendo at gcc dot gnu.org 2014-10-01 21:02 ` olegendo 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-53568-4-9zAbuy3BwE@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).