public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/65702] [5 Regression] ICE (tree check: expected ssa_name, have var_decl in expand_gimple_basic_block, at cfgexpand.c:5506) on arm-linux-gnueabihf Date: Thu, 09 Apr 2015 08:16:00 -0000 [thread overview] Message-ID: <bug-65702-4-QEMgCGxx7m@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65702-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65702 --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- Can't we diagnose this earlier during parsing and avoid making it DECL_HARD_REGISTER in the first place?
next prev parent reply other threads:[~2015-04-09 8:16 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-65702-4@http.gcc.gnu.org/bugzilla/> 2015-04-08 18:21 ` doko at gcc dot gnu.org 2015-04-08 18:25 ` jakub at gcc dot gnu.org 2015-04-08 19:27 ` jakub at gcc dot gnu.org 2015-04-09 8:16 ` rguenth at gcc dot gnu.org [this message] 2015-04-09 8:25 ` jakub at gcc dot gnu.org 2015-04-09 9:15 ` rguenth at gcc dot gnu.org 2015-04-22 12:00 ` [Bug middle-end/65702] [5/6 " jakub at gcc dot gnu.org 2015-07-16 9:20 ` rguenth 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-65702-4-QEMgCGxx7m@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).