From: Jeff Law <law@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>,
Florian Weimer <fweimer@redhat.com>
Cc: Sandra Loosemore <sandra@codesourcery.com>,
"Tsimbalist, Igor V" <igor.v.tsimbalist@intel.com>,
Uros Bizjak <ubizjak@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: 0005-Part-5.-Add-x86-CET-documentation
Date: Thu, 28 Sep 2017 23:29:00 -0000 [thread overview]
Message-ID: <f536e978-bc89-9932-baf6-153d05a3f0f5@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1709271657280.25940@digraph.polyomino.org.uk>
On 09/27/2017 11:01 AM, Joseph Myers wrote:
> On Wed, 27 Sep 2017, Florian Weimer wrote:
>
>> This is part of the ABI GCC implements, so it has to be documented somewhere,
>> and not just as part of the GCC source code.
>>
>> CET is not properly described in the ABI supplement and I don't think this
>> will change, so detailed documentation in the GCC manual is very much
>> desirable.
>
> Isn't this a matter to take up further in the thread HJ started on the ABI
> mailing lists, or a new such thread (possibly e.g. sending pull requests
> that build further on his wording, or propose alternative wording, to
> clarify them things left unclear there, with a goal of getting it clearly
> defined in the master sources for x86_64 and x86)? Clearly the best
> result would be proper documentation in the ABI and the GCC manual
> cross-referencing the relevant ABI documents.
The documentation should be AFAICT independent of the compiler in use --
ie, gcc, llvm and icc all should agree on where/when these new
instructions should be inserted. Which argues that the documentation
belongs in the ABI docs, not the GCC docs. *users* aren't really going
to care about these kinds of details.
So I think the summary is that I agree with Joseph on this. Let's push
it into the ABI docs. HJ can and should play a central role in making
that happen.
jeff
next prev parent reply other threads:[~2017-09-28 23:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 8:57 0005-Part-5.-Add-x86-CET-documentation Tsimbalist, Igor V
2017-09-20 9:21 ` 0005-Part-5.-Add-x86-CET-documentation Tsimbalist, Igor V
2017-09-20 14:13 ` 0005-Part-5.-Add-x86-CET-documentation Uros Bizjak
2017-09-25 3:43 ` 0005-Part-5.-Add-x86-CET-documentation Sandra Loosemore
2017-09-26 13:47 ` 0005-Part-5.-Add-x86-CET-documentation Tsimbalist, Igor V
2017-09-27 3:40 ` 0005-Part-5.-Add-x86-CET-documentation Sandra Loosemore
2017-09-27 8:52 ` 0005-Part-5.-Add-x86-CET-documentation Florian Weimer
2017-09-27 11:52 ` 0005-Part-5.-Add-x86-CET-documentation Tsimbalist, Igor V
2017-09-27 16:48 ` 0005-Part-5.-Add-x86-CET-documentation Sandra Loosemore
2017-09-27 17:01 ` 0005-Part-5.-Add-x86-CET-documentation Joseph Myers
2017-09-28 23:29 ` Jeff Law [this message]
2017-09-27 15:17 ` 0005-Part-5.-Add-x86-CET-documentation Tsimbalist, Igor V
2017-09-28 23:32 ` 0005-Part-5.-Add-x86-CET-documentation Jeff Law
2017-09-29 5:15 ` 0005-Part-5.-Add-x86-CET-documentation Sandra Loosemore
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=f536e978-bc89-9932-baf6-153d05a3f0f5@redhat.com \
--to=law@redhat.com \
--cc=fweimer@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=igor.v.tsimbalist@intel.com \
--cc=joseph@codesourcery.com \
--cc=sandra@codesourcery.com \
--cc=ubizjak@gmail.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).