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] New: Atomic Builtins page should indicate that 16-byte compare-and-swap is available with -mcex16 Date: Fri, 15 Oct 2010 05:03:00 -0000 [thread overview] Message-ID: <bug-46031-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46031 Summary: Atomic Builtins page should indicate that 16-byte compare-and-swap is available with -mcex16 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: web AssignedTo: unassigned@gcc.gnu.org ReportedBy: justin.lebar+bug@gmail.com The atomic builtins page doesn't indicate that gcc supports 16-byte compare-and-swap instructions. But gcc does in fact support this instruction, so the page should indicate that the functionality can be enabled with -mcex16 (or, presumably, with the appropriate -march flag). http://gcc.gnu.org/onlinedocs/gcc/Atomic-Builtins.html
next reply other threads:[~2010-10-15 5:03 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-15 5:03 justin.lebar+bug at gmail dot com [this message] 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
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-46031-4@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).