public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/13626] gcc 4.7 doesn't compile sdt.h with -std=c++0x
Date: Thu, 26 Jan 2012 23:11:00 -0000	[thread overview]
Message-ID: <bug-13626-6586-2XFpGcvVCX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13626-6586@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=13626

Mark Wielaard <mjw at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #2 from Mark Wielaard <mjw at redhat dot com> 2012-01-26 23:11:22 UTC ---
commit 99712e8716e19293fe1f6dd84854d350e57945e0
Author: Mark Wielaard <mjw@redhat.com>
Date:   Thu Jan 26 23:58:38 2012 +0100

    PR13626 Add extra whitespace in sdt.h to deal with C11/C++11 UDF.

    gcc 4.7 supports C11/C++11 user defined literals (UDF):
    https://en.wikipedia.org/wiki/C%2B%2B11#User-defined_literals
    In std=c++0x mode one now needs to add whitespace between string literals.
    See http://gcc.gnu.org/gcc-4.7/porting_to.html

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

      parent reply	other threads:[~2012-01-26 23:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26 22:27 [Bug runtime/13626] New: " mjw at redhat dot com
2012-01-26 22:42 ` [Bug runtime/13626] " mjw at redhat dot com
2012-01-26 23:11 ` mjw at redhat dot com [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=bug-13626-6586-2XFpGcvVCX@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sourceware.org \
    /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).