public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/58814] New: [4.7/4.8/4.9 Regression] ICE with volatile and attribute vector_size Date: Sun, 20 Oct 2013 13:37:00 -0000 [thread overview] Message-ID: <bug-58814-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58814 Bug ID: 58814 Summary: [4.7/4.8/4.9 Regression] ICE with volatile and attribute vector_size Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: reichelt at gcc dot gnu.org The following valid code snippet triggers an ICE since GCC 4.7.0: ==================================================== volatile int i __attribute__((vector_size(8))); void foo() { i += i; } ==================================================== bug.cc: In function 'void foo()': bug.cc:5:5: internal compiler error: in stabilize_expr, at cp/tree.c:3769 i += i; ^ 0x6ef1fe stabilize_expr(tree_node*, tree_node**) ../../gcc/gcc/cp/tree.c:3769 0x68c9f4 cp_build_modify_expr(tree_node*, tree_code, tree_node*, int) ../../gcc/gcc/cp/typeck.c:7362 0x556885 build_new_op_1 ../../gcc/gcc/cp/call.c:5438 0x556f57 build_new_op(unsigned int, tree_code, int, tree_node*, tree_node*, tree_node*, tree_node**, int) ../../gcc/gcc/cp/call.c:5513 0x68e09d build_x_modify_expr(unsigned int, tree_node*, tree_code, tree_node*, int) ../../gcc/gcc/cp/typeck.c:7534 0x651220 cp_parser_assignment_expression ../../gcc/gcc/cp/parser.c:8032 0x653523 cp_parser_expression ../../gcc/gcc/cp/parser.c:8158 0x653d2e cp_parser_expression ../../gcc/gcc/cp/parser.c:8197 0x653d2e cp_parser_expression_statement ../../gcc/gcc/cp/parser.c:9488 0x648fd7 cp_parser_statement ../../gcc/gcc/cp/parser.c:9339 0x64a2c2 cp_parser_statement_seq_opt ../../gcc/gcc/cp/parser.c:9611 0x64a406 cp_parser_compound_statement ../../gcc/gcc/cp/parser.c:9565 0x65da5b cp_parser_function_body ../../gcc/gcc/cp/parser.c:18408 0x65da5b cp_parser_ctor_initializer_opt_and_function_body ../../gcc/gcc/cp/parser.c:18444 0x661e5f cp_parser_function_definition_after_declarator ../../gcc/gcc/cp/parser.c:22452 0x662c32 cp_parser_function_definition_from_specifiers_and_declarator ../../gcc/gcc/cp/parser.c:22373 0x662c32 cp_parser_init_declarator ../../gcc/gcc/cp/parser.c:16419 0x663e7f cp_parser_simple_declaration ../../gcc/gcc/cp/parser.c:11054 0x6477e0 cp_parser_block_declaration ../../gcc/gcc/cp/parser.c:10935 0x66e9fe cp_parser_declaration ../../gcc/gcc/cp/parser.c:10832 Please submit a full bug report, [etc.]
next reply other threads:[~2013-10-20 13:37 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-20 13:37 reichelt at gcc dot gnu.org [this message] 2013-10-20 13:38 ` [Bug c++/58814] " reichelt at gcc dot gnu.org 2013-10-21 9:24 ` mpolacek at gcc dot gnu.org 2013-11-19 10:22 ` rguenth at gcc dot gnu.org 2014-01-27 15:17 ` jason at gcc dot gnu.org 2014-01-28 4:31 ` jason at gcc dot gnu.org 2014-01-28 13:45 ` jason at gcc dot gnu.org 2014-01-28 13:53 ` jason 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-58814-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).