public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ak at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/56619] i386 hle atomic intrinsics flags are undocumented Date: Fri, 15 Mar 2013 04:32:00 -0000 [thread overview] Message-ID: <bug-56619-4-t3T3OA4Mqb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56619-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56619 --- Comment #2 from ak at gcc dot gnu.org 2013-03-15 04:31:53 UTC --- Author: ak Date: Fri Mar 15 04:31:43 2013 New Revision: 196671 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=196671 Log: Document HLE / RTM intrinsics The TSX HLE/RTM intrinsics were missing documentation. Add this to the manual. gcc/: 2013-03-14 Andi Kleen <ak@linux.intel.com> PR target/56619 * doc/extend.texi: Document __ATOMIC_HLE_ACQUIRE, __ATOMIC_HLE_RELEASE. Document __builtin_ia32 TSX intrincs. Document _x* TSX intrinsics. Modified: trunk/gcc/ChangeLog trunk/gcc/doc/extend.texi
next prev parent reply other threads:[~2013-03-15 4:32 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-14 13:16 [Bug target/56619] New: " andi-gcc at firstfloor dot org 2013-03-14 13:18 ` [Bug target/56619] " andi-gcc at firstfloor dot org 2013-03-15 4:32 ` ak at gcc dot gnu.org [this message] 2013-03-15 13:57 ` andi-gcc at firstfloor dot 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-56619-4-t3T3OA4Mqb@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).