public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tim van Deurzen <tim@kompiler.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>,
	Jason Merrill <jason@redhat.com>,
	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Implementing p0515 - spaceship operator
Date: Wed, 10 Jan 2018 21:38:00 -0000	[thread overview]
Message-ID: <d7ad345b-b964-5291-b9c8-75178fa35989@kompiler.org> (raw)
In-Reply-To: <20180110213220.GR1833@tucnak>

Hi Jakub,


On 01/10/2018 10:32 PM, Jakub Jelinek wrote:
> On Wed, Jan 10, 2018 at 10:24:00PM +0100, Tim van Deurzen wrote:
>> On 01/10/2018 02:00 PM, Jonathan Wakely wrote:
>>
>>> On 9 Jan 2018 10:56 p.m., "Tim van Deurzen" wrote:
>>>
>>>
>>>      Just to confirm with you, it does make sense to conditionally
>>>      parse the token for operator<=> in libcpp (i.e. only when the cxx
>>>      standard being used is >=2a)? I'm just wondering if this does not
>>>      accidentally affect other front-ends using libcpp?
>>>
>>>
>>> Other front ends won't setthe language to C++2a.
>>>
>>> I think the relevant check is:
>>>
>>>        if (CPP_OPTION (pfile, lang) == CLK_CXX2A
>>>            || CPP_OPTION (pfile, lang) == CLK_GNUCXX2A)
>>>
>>> This can only be true for a C++ source file when the standard is C++2a.
>>>
>> Ok, good to know, then I'll proceed like this. Thank you!
> Well, the usual way of doing stuff is add another field to
> struct lang_flags, add it to the lang_defaults table, add it to
> struct cpp_options too and then use CPP_OPTION (pfile, spaceship) or so,
> e.g. look how va_opt etc. are implemented.
>
> 	Jakub
I think, I got almost all of that at some point, but probably missed 
something somewhere.
For now I will proceed with the cxx standard flags. If I add any kind of 
warning or toggle I'll have a good idea where to start at this point.
Thank you!

Tim.

  reply	other threads:[~2018-01-10 21:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08 21:07 Tim van Deurzen
2018-01-08 22:08 ` Jason Merrill
2018-01-08 22:13   ` Jonathan Wakely
2018-01-08 22:29     ` Jason Merrill
2018-01-09 22:56       ` Tim van Deurzen
2018-01-10 13:00         ` Jonathan Wakely
2018-01-10 21:24           ` Tim van Deurzen
2018-01-10 21:32             ` Jakub Jelinek
2018-01-10 21:38               ` Tim van Deurzen [this message]
2018-01-11 10:06           ` David Brown
2018-01-11 10:13             ` Jonathan Wakely
2018-01-11 10:15               ` Jonathan Wakely
2018-01-11 11:29               ` David Brown
2018-01-11 11:32                 ` Jonathan Wakely
2018-01-11 11:32                   ` Jonathan Wakely
2018-01-11 11:42                   ` David Brown
2018-01-11 14:06             ` Joseph Myers
2018-08-30 18:07               ` Jakub Jelinek
2018-08-30 18:16                 ` Marek Polacek
2018-09-03 21:04                   ` Tim van Deurzen
2018-09-26 15:01                     ` Jason Merrill
2018-09-27 20:58                       ` Nathan Sidwell
2018-11-05  1:23                       ` Jason Merrill
2018-11-05  7:36                         ` Jason Merrill
2018-11-05  7:40                         ` Tim van Deurzen
2018-11-05  8:07                           ` Jakub Jelinek
2018-11-05 16:03                             ` Tim van Deurzen
2018-11-06 12:35                           ` Jason Merrill
2018-01-09 18:01   ` Nathan Sidwell
2018-01-09 16:10 ` Martin Sebor

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=d7ad345b-b964-5291-b9c8-75178fa35989@kompiler.org \
    --to=tim@kompiler.org \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jason@redhat.com \
    --cc=jwakely.gcc@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).