From: Nick Clifton <nickc@redhat.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] gas: accept custom ".linefile <n> ."
Date: Tue, 15 Nov 2022 11:16:00 +0000 [thread overview]
Message-ID: <3d7ed391-3e7e-c0ce-7d26-c826801cdc98@redhat.com> (raw)
In-Reply-To: <05230a00-0302-c763-02a2-aff573582449@suse.com>
Hi Jan,
>> Alright - in which case we should document it as being unsupported/not
>> for use.
> Okay, if you could give me a hint where undocumented stuff is to go
> in as.texi, I could see about making a patch.
There isn't one. :-)
There is however a node called "AS Sections" which details the assembler
specific sections like .expr. So there is a (very small) precedence for
this kind of thing.
> Otherwise if you would
> make one, it could still educate me in case something else needs
> similar treatment going forward.
OK, I will look into it. In the meantime please consider my suggestion
withdrawn.
Cheers
Nick
next prev parent reply other threads:[~2022-11-15 11:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 7:32 Jan Beulich
2022-11-14 13:43 ` Nick Clifton
2022-11-14 15:53 ` Jan Beulich
2022-11-14 16:02 ` Nick Clifton
2022-11-14 16:16 ` Jan Beulich
2022-11-15 11:16 ` Nick Clifton [this message]
2022-11-15 7:59 ` Jan Beulich
2022-11-15 11:23 ` Nick Clifton
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=3d7ed391-3e7e-c0ce-7d26-c826801cdc98@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.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).