From: Nick Clifton <nickc@redhat.com>
To: Julian Waters <tanksherman27@gmail.com>, binutils@sourceware.org
Subject: Re: [PATCH] SEH: Reimplement the .seh_scope directive
Date: Thu, 20 Jul 2023 12:29:18 +0100 [thread overview]
Message-ID: <4c134506-5ef7-2487-57fb-faaea7787f2f@redhat.com> (raw)
In-Reply-To: <CAP2b4GNq8PqqErerLd_r++AN1VRWPguOmoDq5QqAHpKdcvwL7A@mail.gmail.com>
Hi Julian,
> 3. Where should the documentation be?
gas/doc/c-i386.texi. In the i386-Options section.
(I am right in thinking that these directives are only used for x86_64 PE format binaries, right ?)
> I know what some (but not all) of the directives do, so I'll be happy to document the ones I know
Please do, that would be very helpful.
I also noticed that the directives are mentioned in a comment at the start
of gas/config/obj-coff-seh.h, so if you could add a line for .seh_scope there too
that would be nice.
Cheers Nick
next prev parent reply other threads:[~2023-07-20 11:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 2:33 Julian Waters
2023-07-19 10:53 ` Nick Clifton
2023-07-20 1:48 ` Julian Waters
2023-07-20 11:29 ` Nick Clifton [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-14 8:01 Julian Waters
2023-07-07 9:37 Julian Waters
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=4c134506-5ef7-2487-57fb-faaea7787f2f@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=tanksherman27@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).