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 middle-end/51986] [4.7 regression] uninitialized variable warning regression prevents bootstrap Date: Wed, 25 Jan 2012 14:46:00 -0000 [thread overview] Message-ID: <bug-51986-4-uU8RKIakLV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51986-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51986 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2012-01-25 AssignedTo|unassigned at gcc dot |jakub at gcc dot gnu.org |gnu.org | Ever Confirmed|0 |1 --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-01-25 14:33:39 UTC --- Created attachment 26463 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26463 gcc47-pr51986.patch I think it isn't a false positive, at least from compiler's POV. The compiler can't know that PATTERN (insn) is always non-NULL. I think it is always non-NULL, thus I'm proposing just removing the IMHO unneeded check, if it was actually needed (but then it would need to be scheduler internal, I think most of RTL code assumes everywhere that an insn has non-NULL PATTERN and PATTERN shouldn't be used on non-insns like notes or barriers), we'd want to swap the pat == 0 check with initialization of *rev.
next prev parent reply other threads:[~2012-01-25 14:34 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-24 22:36 [Bug middle-end/51986] New: " matt at use dot net 2012-01-24 22:40 ` [Bug middle-end/51986] " matt at use dot net 2012-01-25 10:57 ` rguenth at gcc dot gnu.org 2012-01-25 14:46 ` jakub at gcc dot gnu.org [this message] 2012-01-25 20:35 ` jakub at gcc dot gnu.org 2012-01-25 21:15 ` 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-51986-4-uU8RKIakLV@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).