public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bilbotheelffriend at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/49551] tentative declaration after definition and -fdata-sections cause ICE in C front-end. Date: Thu, 29 Jan 2015 21:37:00 -0000 [thread overview] Message-ID: <bug-49551-4-GniP2osOzE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49551-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49551 Prathamesh <bilbotheelffriend at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bilbotheelffriend at gmail dot com --- Comment #3 from Prathamesh <bilbotheelffriend at gmail dot com> --- It appears the issue is still present on trunk for arm-none-linux-gnueabihf. Compiling the above code gives following ICE: (arm-none-linux-gnueabihf-gcc -O -fdata-sections): fo.c:2:1: internal compiler error: in get_variable_section, at varasm.c:1151 int x; ^ 0xd1b9ab get_variable_section(tree_node*, bool) /home/prathamesh.kulkarni/arm-gnu-toolchain/src/gcc.git~master/gcc/varasm.c:1150 0xd1ca81 get_block_for_decl /home/prathamesh.kulkarni/arm-gnu-toolchain/src/gcc.git~master/gcc/varasm.c:1216 0xd1e50f make_decl_rtl(tree_node*) /home/prathamesh.kulkarni/arm-gnu-toolchain/src/gcc.git~master/gcc/varasm.c:1346 0x5301fc duplicate_decls /home/prathamesh.kulkarni/arm-gnu-toolchain/src/gcc.git~master/gcc/c/c-decl.c:2732 0x533400 pushdecl(tree_node*) /home/prathamesh.kulkarni/arm-gnu-toolchain/src/gcc.git~master/gcc/c/c-decl.c:2888 0x5457d6 start_decl(c_declarator*, c_declspecs*, bool, tree_node*) /home/prathamesh.kulkarni/arm-gnu-toolchain/src/gcc.git~master/gcc/c/c-decl.c:4626 0x595d7e c_parser_declaration_or_fndef /home/prathamesh.kulkarni/arm-gnu-toolchain/src/gcc.git~master/gcc/c/c-parser.c:1846 0x5a07b8 c_parser_external_declaration /home/prathamesh.kulkarni/arm-gnu-toolchain/src/gcc.git~master/gcc/c/c-parser.c:1452 0x5a1215 c_parser_translation_unit /home/prathamesh.kulkarni/arm-gnu-toolchain/src/gcc.git~master/gcc/c/c-parser.c:1339 0x5a1215 c_parse_file() /home/prathamesh.kulkarni/arm-gnu-toolchain/src/gcc.git~master/gcc/c/c-parser.c:15416 0x5fd622 c_common_parse_file() /home/prathamesh.kulkarni/arm-gnu-toolchain/src/gcc.git~master/gcc/c-family/c-opts.c:1052 Thanks, Prathamesh
next prev parent reply other threads:[~2015-01-29 21:37 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-27 18:27 [Bug c/49551] New: common variables " dougkwan at google dot com 2011-06-27 20:48 ` [Bug c/49551] " dougkwan at google dot com 2014-09-24 17:58 ` [Bug target/49551] tentative declaration after definition " mpolacek at gcc dot gnu.org 2015-01-29 21:37 ` bilbotheelffriend at gmail dot com [this message] 2015-06-02 16:43 ` prathamesh3492 at gcc dot gnu.org 2015-06-02 16:46 ` prathamesh3492 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-49551-4-GniP2osOzE@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).