Re: Implementing p0515 - spaceship operator

[Jonathan Wakely]

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.

Re: Bugzilla admin?

[Jakub Jelinek]

On Wed, Jan 10, 2018 at 02:30:39PM +, Andrew Haley wrote:
> I don't seem to have write access to bugs in GCC Bugzilla.  I'm pretty
> sure I used to have it.  Who do I contact?  Thanks.

You need to use the @gcc.gnu.org account to have write access to bugzilla,
using some other account usually doesn't work.

Jakub

Re: Bugzilla admin?

[Jonathan Wakely]

On 10 January 2018 at 14:33, Jakub Jelinek wrote:
> On Wed, Jan 10, 2018 at 02:30:39PM +, Andrew Haley wrote:
>> I don't seem to have write access to bugs in GCC Bugzilla.  I'm pretty
>> sure I used to have it.  Who do I contact?  Thanks.
>
> You need to use the @gcc.gnu.org account to have write access to bugzilla,
> using some other account usually doesn't work.

And we don't usually give bugzilla privs to n...@gcc.gnu.org accounts,
because most people who need privs already have an @gcc.gnu.org
account for svn write access anyway.

Bugzilla admin?

[Andrew Haley]

I don't seem to have write access to bugs in GCC Bugzilla.  I'm pretty
sure I used to have it.  Who do I contact?  Thanks.

-- 
Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. 
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671

Re: Bugzilla admin?

[Andrew Haley]

On 10/01/18 14:33, Jakub Jelinek wrote:
> On Wed, Jan 10, 2018 at 02:30:39PM +, Andrew Haley wrote:
>> I don't seem to have write access to bugs in GCC Bugzilla.  I'm pretty
>> sure I used to have it.  Who do I contact?  Thanks.
> 
> You need to use the @gcc.gnu.org account to have write access to bugzilla,
> using some other account usually doesn't work.

Aha!  That was it, thanks.

-- 
Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. 
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671

Re: Implementing p0515 - spaceship operator

[Tim van Deurzen]

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!

Tim.

Re: Implementing p0515 - spaceship operator

[Jakub Jelinek]

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

Re: Implementing p0515 - spaceship operator

[Tim van Deurzen]

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.

gcc-6-20180110 is now available

[gccadmin]

Snapshot gcc-6-20180110 is now available on
  ftp://gcc.gnu.org/pub/gcc/snapshots/6-20180110/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.

This snapshot has been generated from the GCC 6 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-6-branch 
revision 256458

You'll find:

 gcc-6-20180110.tar.xzComplete GCC

  SHA256=570cfc8d6aa21bf39d5508038dfb1a79f9f1bff14f07099c375ba130f1b001f4
  SHA1=2f2b6ede96b5f62bf719530fdb5ff1e78b69780f

Diffs from 6-20180103 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-6
link is updated and a message is sent to the gcc list.  Please do not use
a snapshot before it has been announced that way.