public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/57543] decltype needs explicit 'this' pointer in member function declaration of template class with trailing return type
Date: Sat, 08 Jun 2013 14:51:00 -0000 [thread overview]
Message-ID: <bug-57543-4-WY4OlZaxcr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57543-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57543
Daniel Krügler <daniel.kruegler at googlemail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |daniel.kruegler@googlemail.
| |com
--- Comment #1 from Daniel Krügler <daniel.kruegler at googlemail dot com> ---
This problem still exists for gcc 4.9.0 20130519 (experimental)
>From gcc-bugs-return-424031-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jun 08 15:12:09 2013
Return-Path: <gcc-bugs-return-424031-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15589 invoked by alias); 8 Jun 2013 15:12:08 -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 15336 invoked by uid 48); 8 Jun 2013 15:12:02 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/57524] internal compiler error on dump translation unit
Date: Sat, 08 Jun 2013 15:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.7.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: NEW
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: bug_status cf_reconfirmed_on everconfirmed cf_known_to_fail
Message-ID: <bug-57524-4-LKMFA6RQCB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-57524-4@http.gcc.gnu.org/bugzilla/>
References: <bug-57524-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: 2013-06/txt/msg00410.txt.bz2
Content-length: 2597
http://gcc.gnu.org/bugzilla/show_bug.cgi?idW524
Marc Glisse <glisse at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed|2013-06-05 00:00:00 |2013-06-08
Ever confirmed|0 |1
Known to fail| |4.7.3, 4.8.0
--- Comment #9 from Marc Glisse <glisse at gcc dot gnu.org> ---
Calling cc1plus directly, I can reproduce with trunk. The failing assert in
timevar.c is:
/* Don't allow the same timing variable to be started more than
once. */
gcc_assert (!tv->standalone);
/usr/include/boost/variant/detail/hash_variant.hpp:33:24: internal compiler
error: in timevar_start, at timevar.c:343
0xcce161 timevar_start(timevar_id_t)
/data/repos/gcc/trunk/gcc/timevar.c:343
0x7cfa85 push_using_directive
/data/repos/gcc/trunk/gcc/cp/name-lookup.c:5652
0x7cfa34 push_using_directive_1
/data/repos/gcc/trunk/gcc/cp/name-lookup.c:5641
0x7cfa91 push_using_directive
/data/repos/gcc/trunk/gcc/cp/name-lookup.c:5653
0x7ca70e do_using_directive(tree_node*)
/data/repos/gcc/trunk/gcc/cp/name-lookup.c:3933
0x7ca7a7 parse_using_directive(tree_node*, tree_node*)
/data/repos/gcc/trunk/gcc/cp/name-lookup.c:3957
0x6ddce4 cp_parser_using_directive
/data/repos/gcc/trunk/gcc/cp/parser.c:15732
0x6d5ceb cp_parser_block_declaration
/data/repos/gcc/trunk/gcc/cp/parser.c:10670
0x6d53df cp_parser_declaration_statement
/data/repos/gcc/trunk/gcc/cp/parser.c:10344
0x6d2e33 cp_parser_statement
/data/repos/gcc/trunk/gcc/cp/parser.c:9107
0x6d371b cp_parser_statement_seq_opt
/data/repos/gcc/trunk/gcc/cp/parser.c:9379
0x6d361e cp_parser_compound_statement
/data/repos/gcc/trunk/gcc/cp/parser.c:9333
0x6e1e23 cp_parser_function_body
/data/repos/gcc/trunk/gcc/cp/parser.c:18066
0x6e20b0 cp_parser_ctor_initializer_opt_and_function_body
/data/repos/gcc/trunk/gcc/cp/parser.c:18102
0x6e8f28 cp_parser_function_definition_after_declarator
/data/repos/gcc/trunk/gcc/cp/parser.c:22080
0x6eab72 cp_parser_late_parsing_for_member
/data/repos/gcc/trunk/gcc/cp/parser.c:22730
0x6e36cc cp_parser_class_specifier_1
/data/repos/gcc/trunk/gcc/cp/parser.c:18825
0x6e3795 cp_parser_class_specifier
/data/repos/gcc/trunk/gcc/cp/parser.c:18849
0x6da899 cp_parser_type_specifier
/data/repos/gcc/trunk/gcc/cp/parser.c:13861
0x6d66b4 cp_parser_decl_specifier_seq
/data/repos/gcc/trunk/gcc/cp/parser.c:11152
next prev parent reply other threads:[~2013-06-08 14:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 11:53 [Bug c++/57543] New: decltype needs eplicity " mitchnull+gcc at gmail dot com
2013-06-06 20:46 ` [Bug c++/57543] decltype needs explicit " paolo.carlini at oracle dot com
2013-06-08 14:51 ` daniel.kruegler at googlemail dot com [this message]
2013-12-01 13:40 ` d.frey at gmx dot de
2014-05-27 10:44 ` paolo.carlini at oracle dot com
2014-05-28 16:04 ` paolo.carlini at oracle dot com
2014-05-29 13:53 ` paolo.carlini at oracle dot com
2014-05-29 17:12 ` paolo.carlini at oracle dot com
2014-05-31 8:52 ` paolo.carlini at oracle dot com
2014-05-31 8:52 ` paolo at gcc dot gnu.org
2014-06-03 9:55 ` 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-57543-4-WY4OlZaxcr@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).