From: Andi Kleen <andi@firstfloor.org>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>,
gcc-patches@gcc.gnu.org, Andi Kleen <ak@linux.intel.com>,
Richard Henderson <rth@redhat.com>
Subject: Re: [PATCH 1/2] Document HLE / RTM intrinsics
Date: Mon, 14 Jan 2013 18:22:00 -0000 [thread overview]
Message-ID: <20130114182203.GB30577@one.firstfloor.org> (raw)
In-Reply-To: <CAFiYyc0+7jQB7QWUb+wevwtUcW2=uep6S_deJDdfmM06dAzSAA@mail.gmail.com>
> I think (somewhere else) we agreed to only document intrinsics,
> not the __builtin_ia32_ variants (they are an implementation detail).
They are all (poorly) documented.
I didn't really document them, just list them.
> Yes, we're not consistent with that, but we do miss a lot of
> documentation for these kind of builtins. I suppose we also do not
> document all intrinsics either (though that's desired, as we provide
> those headers - even manpages would be nice for them I suppose).
It would be nice if gcc had proper documentation for all the
<xxxintrin.h> functions. But that's a lot of work.
But I would like to have TSX properly documented at least.
-Andi
next prev parent reply other threads:[~2013-01-14 18:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 15:29 Andi Kleen
2013-01-12 15:29 ` [PATCH 2/2] Support __ATOMIC_HLE_RELEASE for __atomic_clear/store_n Andi Kleen
2013-01-12 17:02 ` [PATCH 1/2] Document HLE / RTM intrinsics Bernhard Reutner-Fischer
2013-01-12 17:20 ` Andi Kleen
2013-01-14 14:44 ` Richard Biener
2013-01-14 18:22 ` Andi Kleen [this message]
2013-01-20 18:50 ` [PING] " Andi Kleen
2013-01-26 22:55 ` [PING^2] " Andi Kleen
2013-02-14 21:34 ` [PING^3] " Andi Kleen
2013-01-27 18:16 ` Florian Weimer
2013-01-27 21:22 ` Andi Kleen
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=20130114182203.GB30577@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=ak@linux.intel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rep.dot.nop@gmail.com \
--cc=richard.guenther@gmail.com \
--cc=rth@redhat.com \
/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).