From: Borislav Petkov <bp@suse.de>
To: gcc-patches@gcc.gnu.org
Cc: Michael Matz <matz@suse.de>, Richard Biener <rguenther@suse.de>
Subject: Re: [PATCH] Document some arch-specific operand modifiers
Date: Tue, 17 Apr 2018 15:42:00 -0000 [thread overview]
Message-ID: <20180417154203.GH18808@pd.tnic> (raw)
In-Reply-To: <20180314163521.GH3173@pd.tnic>
On Wed, Mar 14, 2018 at 05:35:21PM +0100, Borislav Petkov wrote:
> Hi,
>
> here's an attempt to document some of the inline asm operand modifiers
> which make sense and which get used so that people can find what they
> mean in the docs.
>
> This is my first gcc patch so there might be clumsiness ahead. :)
>
> Thanks,
> Boris.
>
> gcc/Changelog:
>
> 2018-03-14 Borislav Petkov <bp@suse.de>
>
> * gcc/doc/extend.texi: document some arch-specific asm operand modifiers
> and sort entries.
> * gcc/config/i386/i386.c: fix typo.
Looks forgotten, lemme ping people...
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
next prev parent reply other threads:[~2018-04-17 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 17:05 Borislav Petkov
2018-04-17 15:42 ` Borislav Petkov [this message]
2018-05-30 22:56 ` Jeff Law
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=20180417154203.GH18808@pd.tnic \
--to=bp@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=matz@suse.de \
--cc=rguenther@suse.de \
/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).