From: Segher Boessenkool <segher@kernel.crashing.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, jakub@redhat.com, polacek@redhat.com,
jason@redhat.com, nathan@acm.org
Subject: Re: [PATCH 1/2] asm qualifiers (PR55681)
Date: Fri, 30 Nov 2018 00:21:00 -0000 [thread overview]
Message-ID: <20181130002101.GR23873@gate.crashing.org> (raw)
In-Reply-To: <alpine.DEB.2.21.1811300008130.27172@digraph.polyomino.org.uk>
On Fri, Nov 30, 2018 at 12:11:30AM +0000, Joseph Myers wrote:
> On Thu, 29 Nov 2018, Segher Boessenkool wrote:
>
> > So "asm const restrict" is allowed, but "asm const const restrict" isn't.
>
> No, asm const restrict isn't allowed. volatile is allowed; const and
> restrict are allowed with warnings because that replicates what the old
> bison parser allowed; but at most one qualifier is allowed at present.
I mean the wanted behaviour, not the current behaviour.
> > What do you want done with const and restrict (and _Atomic, which is
> > allowed by the current grammar)?
>
> Don't allow _Atomic, since it's not allowed at present. Either allow at
> most one qualifier (being one of volatile / const / restrict) or remove
> support for const and restrict there and just allow (at most one)
> volatile.
I'll go for the latter. That also harmonises C and C++ here.
Thanks!
Segher
next prev parent reply other threads:[~2018-11-30 0:21 UTC|newest]
Thread overview: 23+ 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 [this message]
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:39 ` [PATCH 1/2] asm qualifiers (PR55681) Segher Boessenkool
2018-12-03 22:20 ` Joseph Myers
2018-12-05 21:47 ` Jason Merrill
2018-12-05 23:02 ` 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=20181130002101.GR23873@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=joseph@codesourcery.com \
--cc=nathan@acm.org \
--cc=polacek@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).