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 c++/65558] New: crash using __attribute__((__abi_tag__)) on anonymous inline namespace Date: Wed, 25 Mar 2015 16:55:00 -0000 [thread overview] Message-ID: <bug-65558-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65558 Bug ID: 65558 Summary: crash using __attribute__((__abi_tag__)) on anonymous inline namespace Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: trippels at gcc dot gnu.org CC: jason at gcc dot gnu.org markus@x4 tmp % cat n.ii inline namespace __attribute__((__abi_tag__)) {} markus@x4 tmp % g++ -c n.ii n.ii:1:47: internal compiler error: Segmentation fault inline namespace __attribute__((__abi_tag__)) {} ^ 0xcaf40f crash_signal ../../gcc/gcc/toplev.c:383 0x7daa72 tree_check(tree_node*, char const*, int, char const*, tree_code) ../../gcc/gcc/tree.h:2845 0x7daa72 handle_namespace_attrs(tree_node*, tree_node*) ../../gcc/gcc/cp/name-lookup.c:3670 0x73867c cp_parser_namespace_definition ../../gcc/gcc/cp/parser.c:16247 0x737c69 cp_parser_declaration ../../gcc/gcc/cp/parser.c:11366 0x737dfa cp_parser_declaration_seq_opt ../../gcc/gcc/cp/parser.c:11264 0x73810f cp_parser_translation_unit ../../gcc/gcc/cp/parser.c:4100 0x73810f c_parse_file() ../../gcc/gcc/cp/parser.c:33193 0x869c12 c_common_parse_file() ../../gcc/gcc/c-family/c-opts.c:1057 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <http://gcc.gnu.org/bugs.html> for instructions.
next reply other threads:[~2015-03-25 16:40 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-25 16:55 trippels at gcc dot gnu.org [this message] 2015-03-25 18:00 ` [Bug c++/65558] [5 Regression] " mpolacek at gcc dot gnu.org 2015-03-25 18:07 ` redi at gcc dot gnu.org 2015-03-25 18:13 ` mpolacek at gcc dot gnu.org 2015-03-25 19:24 ` jason at gcc dot gnu.org 2015-03-25 20:38 ` mpolacek at gcc dot gnu.org 2015-03-25 21:19 ` mpolacek 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-65558-4@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: linkBe 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).