public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52624] Missing __builtin_bswap16
Date: Thu, 22 Mar 2012 07:54:00 -0000 [thread overview]
Message-ID: <bug-52624-4-grPTokfMrA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52624-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52624
--- Comment #5 from Uros Bizjak <ubizjak at gmail dot com> 2012-03-22 07:51:20 UTC ---
(In reply to comment #4)
> I think that it should be available on all architectures, like the 32-bit and
> 64-bit flavors. And, for x86, you don't really need to add new patterns.
I agree.
Regarding new patterns - we need at least named expander, and the existing ones
are strict_low_part types. They model the fact that higpart of the register is
preserved, so ideal to implement bswap32.
Can you please take the middle-end part of the generic implementation?
next prev parent reply other threads:[~2012-03-22 7:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 18:01 [Bug target/52624] New: " hjl.tools at gmail dot com
2012-03-19 18:31 ` [Bug target/52624] " pinskia at gcc dot gnu.org
2012-03-21 16:18 ` ebotcazou at gcc dot gnu.org
2012-03-22 0:00 ` ubizjak at gmail dot com
2012-03-22 7:49 ` ebotcazou at gcc dot gnu.org
2012-03-22 7:54 ` ubizjak at gmail dot com [this message]
2012-03-22 8:07 ` ebotcazou at gcc dot gnu.org
2012-03-22 8:29 ` [Bug target/52624] missing __builtin_bswap16 ebotcazou at gcc dot gnu.org
2012-03-22 10:05 ` ubizjak at gmail dot com
2012-03-22 10:09 ` ebotcazou at gcc dot gnu.org
2012-03-22 16:25 ` hjl.tools at gmail dot com
2012-03-22 17:04 ` ubizjak at gmail dot com
2012-04-11 11:13 ` ebotcazou at gcc dot gnu.org
2012-04-11 11:19 ` ebotcazou 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-52624-4-grPTokfMrA@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).