public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Jason Merrill <jason@redhat.com>,gcc-patches List
	<gcc-patches@gcc.gnu.org>
Subject: Re: PATCHes to help with C++11 bootstrap
Date: Sat, 09 May 2015 10:37:00 -0000	[thread overview]
Message-ID: <F30A76B2-442B-4787-8738-7D6C26C629E8@gmail.com> (raw)
In-Reply-To: <554D8D79.9080502@redhat.com>

On May 9, 2015 6:30:49 AM GMT+02:00, Jason Merrill <jason@redhat.com> wrote:
>One C++11 compatibility issue that turns up a lot in the GCC sources is
>
>that in C++98,
>
>#define BAR "bar"
>const char *p = "foo"BAR;
>
>is well-formed, giving p the value "foobar".  But in C++11 this is a 
>user-defined literal with the suffix BAR, which is ill-formed because 
>there is no BAR suffix defined.
>
>-Wc++11-compat didn't warn about this, which I'm fixing with the first 
>patch.
>
>The second patch fixes all the occurrences in GCC.
>
>The third patch fixes the warning to say "-Wc++11-compat" rather than 
>"-Wc++0x-compat".
>
>The fourth patch fixes a few G++ tests that were failing with the 
>compiler defaulting to C++11.
>
>Tested x86_64-cp-linux-gnu, applying to trunk.

Hmm, I wonder if we want to bootstrap with explicit -std=gnu04, our host compiler requirement.  Otherwise we'll silently sneak in C++11 features when that becomes the default?

Richard.


  reply	other threads:[~2015-05-09 10:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-09  4:31 Jason Merrill
2015-05-09 10:37 ` Richard Biener [this message]
2015-05-10  0:44   ` Jason Merrill
2015-07-11 10:16     ` Hans-Peter Nilsson
2015-05-09 18:27 ` Markus Trippelsdorf
2015-05-09 21:50   ` Jason Merrill
2015-05-09 21:54 ` Jason Merrill
2015-05-11 11:30 ` Markus Trippelsdorf
2015-05-13  3:31   ` Jason Merrill

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=F30A76B2-442B-4787-8738-7D6C26C629E8@gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@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).