From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Neven Sajko <nsajko@gmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Doc fix request: C/C++ extended asm empty input constraint
Date: Mon, 22 Feb 2021 14:27:59 +0000 [thread overview]
Message-ID: <CAH6eHdRH0tk-23U354itX1wbJKyvYiwW3MAM2RFz1W5ON33dmg@mail.gmail.com> (raw)
In-Reply-To: <CAL+bK4P=FGqZ-w0CDUUAZ-Gj3G+CMKXz0r5r7gZU6W+Br+nhgg@mail.gmail.com>
On Mon, 22 Feb 2021 at 02:17, Neven Sajko <nsajko@gmail.com> wrote:
>
> On Mon, 15 Feb 2021 at 08:11, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> >
> >
> >
> > On Mon, 15 Feb 2021, 00:48 Neven Sajko via Gcc, <gcc@gcc.gnu.org> wrote:
> >>
> >>
> >> This is why I am asking for this feature to be documented. It seems
> >> like this would be the most appropriate place:
> >> https://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html#InputOperands
> >>
> >> I would have tried to contribute a doc fix myself, but I couldn't find
> >> the sources for the online docs in the GCC Git repository.
> >
> >
> >
> > git grep is your friend. The relevant section is:
> >
> > https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/doc/extend.texi;h=e110cb010617bfb78e740433c3aa30a7399b504e;hb=HEAD#l10344
>
> I posted a patch back then (a week ago) to gcc-patches, but there was
> no response. I'm not complaining, but I wonder if I should maybe ping
> a developer interested in the extended asm extension specifically? Who
> might that be?
I don't think there is a maintainer for asm statements, but a docs
maintainer might be relevant for this patch. You can also just ping
the patch by replying to it on the list, without CCing anybody
particular.
> This is the patch in the archive:
> https://gcc.gnu.org/pipermail/gcc-patches/2021-February/565339.html
I replied to the mail.
prev parent reply other threads:[~2021-02-22 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 0:40 Neven Sajko
2021-02-15 8:11 ` Jonathan Wakely
2021-02-22 2:16 ` Neven Sajko
2021-02-22 14:27 ` Jonathan Wakely [this message]
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=CAH6eHdRH0tk-23U354itX1wbJKyvYiwW3MAM2RFz1W5ON33dmg@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=nsajko@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).