public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/52132] New: [4.7 Regression] ICE in loc_descriptor Date: Mon, 06 Feb 2012 08:32:00 -0000 [thread overview] Message-ID: <bug-52132-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52132 Bug #: 52132 Summary: [4.7 Regression] ICE in loc_descriptor Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: debug AssignedTo: jakub@gcc.gnu.org ReportedBy: jakub@gcc.gnu.org Target: i686-linux The following testcase ICEs with -m32 -g -O2 -std=c99 on x86_64-linux. The bug is likely in regstack, which changes: rh787518.i.216r.sched2:(debug_insn 20 58 21 2 (var_location:SI D#1 (subreg:SI (reg:SF 8 st [orig:66 D.1248 ] [66]) 0)) rh787518.i:10 -1 to: rh787518.i.218r.stack:(debug_insn 20 58 21 2 (var_location:SI D#1 (reg:SF 8 st)) rh787518.i:10 -1 (note the lost subreg). The regression started with http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=178597 though that likely just made a latent bug into a reprduceable one.
next reply other threads:[~2012-02-06 8:32 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-06 8:32 jakub at gcc dot gnu.org [this message] 2012-02-06 8:33 ` [Bug debug/52132] " jakub at gcc dot gnu.org 2012-02-06 8:34 ` jakub at gcc dot gnu.org 2012-02-06 10:24 ` jakub at gcc dot gnu.org 2012-02-06 23:00 ` p.finizio at gmail dot com 2012-02-06 23:02 ` p.finizio at gmail dot com 2012-02-07 15:49 ` rguenth at gcc dot gnu.org 2012-02-11 8:28 ` jakub at gcc dot gnu.org 2012-02-11 8:32 ` jakub 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-52132-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).