public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/64367] [5 Regression] g++-v5/stdexcept:52:28: error: invalid use of non-static data member '_M_p'
Date: Sat, 20 Dec 2014 14:02:00 -0000 [thread overview]
Message-ID: <bug-64367-4-HxlxOQ5FED@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64367-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64367
--- Comment #3 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
See § 5.1.1-13 for C++11 and § 5.1-10 for C++98.
The C++98 standard doesn't mention unevaluated operands.
>From gcc-bugs-return-471446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 20 14:23:38 2014
Return-Path: <gcc-bugs-return-471446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29071 invoked by alias); 20 Dec 2014 14:23:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29046 invoked by uid 48); 20 Dec 2014 14:23:32 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/64367] [5 Regression] g++-v5/stdexcept:52:28: error: invalid use of non-static data member '_M_p'
Date: Sat, 20 Dec 2014 14:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-64367-4-MzcPC3GKqX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64367-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64367-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-12/txt/msg02453.txt.bz2
Content-length: 203
https://gcc.gnu.org/bugzilla/show_bug.cgi?idd367
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Oh it's only for 98, I see.
Well it's easy to fix with sizeof(const char*) anyway.
next prev parent reply other threads:[~2014-12-20 14:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-20 11:43 [Bug libstdc++/64367] New: " trippels at gcc dot gnu.org
2014-12-20 13:02 ` [Bug libstdc++/64367] " redi at gcc dot gnu.org
2014-12-20 13:31 ` trippels at gcc dot gnu.org
2014-12-20 14:02 ` trippels at gcc dot gnu.org [this message]
2014-12-21 15:16 ` redi at gcc dot gnu.org
2014-12-21 15:17 ` redi at gcc dot gnu.org
2015-02-26 17:12 ` redi at gcc dot gnu.org
2015-03-02 16:51 ` redi at gcc dot gnu.org
2015-03-02 16:52 ` redi at gcc dot gnu.org
2015-03-12 12:57 ` redi at gcc dot gnu.org
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-64367-4-HxlxOQ5FED@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).