From: Marek Polacek <polacek@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: gcc-patches@gcc.gnu.org, jakub@redhat.com
Subject: Re: [PATCH 2/2] asm inline
Date: Tue, 30 Oct 2018 18:58:00 -0000 [thread overview]
Message-ID: <20181030173935.GN6974@redhat.com> (raw)
In-Reply-To: <e59a75e62603e73c299550dc50b2f61a668f53ca.1540918534.git.segher@kernel.crashing.org>
On Tue, Oct 30, 2018 at 05:30:34PM +0000, Segher Boessenkool wrote:
> --- a/gcc/c/c-typeck.c
> +++ b/gcc/c/c-typeck.c
> @@ -10064,7 +10064,7 @@ build_asm_stmt (tree cv_qualifier, tree args)
> are subtly different. We use a ASM_EXPR node to represent this. */
> tree
> build_asm_expr (location_t loc, tree string, tree outputs, tree inputs,
> - tree clobbers, tree labels, bool simple)
> + tree clobbers, tree labels, bool simple, bool is_inline)
The new parameter should probably be described in the comment above.
Marek
next prev parent reply other threads:[~2018-10-30 17:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 18:01 [PATCH 0/2] asm qualifiers (PR55681) and asm input Segher Boessenkool
2018-10-30 18:41 ` [PATCH 2/2] asm inline Segher Boessenkool
2018-10-30 18:58 ` Marek Polacek [this message]
2018-11-11 21:33 ` Martin Sebor
2018-11-11 22:01 ` Segher Boessenkool
2018-11-11 23:41 ` Martin Sebor
2018-11-12 0:19 ` Segher Boessenkool
2018-11-30 13:14 ` Richard Biener
2018-10-30 18:56 ` [PATCH 1/2] asm qualifiers (PR55681) Segher Boessenkool
2018-11-29 13:35 ` Segher Boessenkool
2018-11-29 21:13 ` Joseph Myers
2018-11-29 22:22 ` Segher Boessenkool
2018-11-29 23:14 ` Joseph Myers
2018-11-30 0:03 ` Segher Boessenkool
2018-11-30 0:11 ` Joseph Myers
2018-11-30 0:21 ` Segher Boessenkool
2018-11-11 0:33 ` [PATCH 0/2] asm qualifiers (PR55681) and asm input Segher Boessenkool
2018-11-17 14:53 ` Segher Boessenkool
2018-11-29 12:27 ` [ping x3] Re: [PATCH 0/2] asm qualifiers (PR55681) and asm inline Segher Boessenkool
2018-12-02 16:38 [PATCH v2 " Segher Boessenkool
2018-12-02 16:40 ` [PATCH 2/2] " Segher Boessenkool
2018-12-02 17:23 ` Marc Glisse
2018-12-02 17:45 ` Segher Boessenkool
2018-12-02 18:38 ` Marc Glisse
2018-12-04 15:31 ` Richard Sandiford
2018-12-06 3:03 ` Segher Boessenkool
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=20181030173935.GN6974@redhat.com \
--to=polacek@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=segher@kernel.crashing.org \
/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).