public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "justin.lebar+bug at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/46031] Atomic Builtins page should indicate that 16-byte compare-and-swap is available with -mcex16
Date: Fri, 15 Oct 2010 05:54:00 -0000 [thread overview]
Message-ID: <20101015055400.fkV75GzgkMrUDv8mew9TLZG1GA7SRLW_c6spLqKDyBY@z> (raw)
In-Reply-To: <bug-46031-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46031
--- Comment #4 from Justin Lebar <justin.lebar+bug at gmail dot com> 2010-10-15 05:54:28 UTC ---
> Actually it says the target processors might not include all of the builtins.
Maybe I'm not making sense. My point is that there's a builtin (*) that is
supported by some target processors but is not listed in the manual. So the
statement that some target processors might not include all the builtins isn't
helpful.
* The builtin is compare_and_swap with 16-byte operands. The manual explicitly
says "GCC will allow any integral scalar or pointer type that is 1, 2, 4 or 8
bytes in length" but should indicate that 16-byte operands are supported for
compare_and_swap, at least under some circumstances.
prev parent reply other threads:[~2010-10-15 5:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 5:03 [Bug web/46031] New: " justin.lebar+bug at gmail dot com
2010-10-15 5:08 ` [Bug web/46031] " pinskia at gcc dot gnu.org
2010-10-15 5:30 ` justin.lebar+bug at gmail dot com
2010-10-15 5:40 ` pinskia at gcc dot gnu.org
2010-10-15 5:54 ` justin.lebar+bug at gmail dot com [this message]
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=20101015055400.fkV75GzgkMrUDv8mew9TLZG1GA7SRLW_c6spLqKDyBY@z \
--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).