public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: gcc-patches@gcc.gnu.org
Cc: jakub@redhat.com
Subject: [ping x3] Re: [PATCH 0/2] asm qualifiers (PR55681) and asm inline
Date: Thu, 29 Nov 2018 12:27:00 -0000	[thread overview]
Message-ID: <20181129122703.GY23873@gate.crashing.org> (raw)
In-Reply-To: <20181117145258.GR23873@gate.crashing.org>

Ping x3.

On Sat, Nov 17, 2018 at 08:52:58AM -0600, Segher Boessenkool wrote:
> Ping x2.
> 
> On Sat, Nov 10, 2018 at 06:33:37PM -0600, Segher Boessenkool wrote:
> > Ping.
> > 
> > On Tue, Oct 30, 2018 at 05:30:32PM +0000, Segher Boessenkool wrote:
> > > Hi!
> > > 
> > > This is the same "asm input" patch as before, but now preceded by a patch
> > > that makes all orderings of volatile/goto/inline valid, also the other type
> > > qualifiers for C, and also repetitions for C.
> > > 
> > > Tested on powerpc64-linux {-m32,-m64}.  Is this okay for trunk?
> > > 
> > > 
> > > Segher
> > > 
> > > 
> > >  gcc/c/c-parser.c                                | 79 ++++++++++++---------
> > >  gcc/c/c-tree.h                                  |  3 +-
> > >  gcc/c/c-typeck.c                                |  3 +-
> > >  gcc/cp/cp-tree.h                                |  2 +-
> > >  gcc/cp/parser.c                                 | 92 +++++++++++++++++--------
> > >  gcc/cp/pt.c                                     |  2 +-
> > >  gcc/cp/semantics.c                              |  3 +-
> > >  gcc/doc/extend.texi                             | 10 ++-
> > >  gcc/gimple-pretty-print.c                       |  2 +
> > >  gcc/gimple.h                                    | 24 ++++++-
> > >  gcc/gimplify.c                                  |  1 +
> > >  gcc/ipa-icf-gimple.c                            |  3 +
> > >  gcc/testsuite/c-c++-common/torture/asm-inline.c | 53 ++++++++++++++
> > >  gcc/tree-core.h                                 |  3 +
> > >  gcc/tree-inline.c                               |  3 +
> > >  gcc/tree.h                                      |  3 +
> > >  16 files changed, 221 insertions(+), 65 deletions(-)
> > >  create mode 100644 gcc/testsuite/c-c++-common/torture/asm-inline.c
> > > 
> > > -- 
> > > 1.8.3.1

      reply	other threads:[~2018-11-29 12:27 UTC|newest]

Thread overview: 19+ 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
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     ` Segher Boessenkool [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=20181129122703.GY23873@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.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).