public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/58759] [4.9 Regression] wrong code (segfaults) at -O2 on x86_64-linux-gnu in 32-bit mode Date: Thu, 17 Oct 2013 14:31:00 -0000 [thread overview] Message-ID: <bug-58759-4-mXLjs4Cr0H@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58759-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58759 --- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Seem to be RTL cprop, more specifically, local_cprop_pass.
next prev parent reply other threads:[~2013-10-17 14:31 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-16 22:00 [Bug tree-optimization/58759] New: " su at cs dot ucdavis.edu 2013-10-17 8:46 ` [Bug tree-optimization/58759] [4.9 Regression] " mpolacek at gcc dot gnu.org 2013-10-17 14:31 ` mpolacek at gcc dot gnu.org [this message] 2013-10-20 15:08 ` [Bug rtl-optimization/58759] " mikpelinux at gmail dot com 2013-10-21 15:52 ` law at redhat dot com 2013-10-24 20:36 ` vmakarov at gcc dot gnu.org 2013-10-25 21:34 ` vmakarov at gcc dot gnu.org 2013-11-05 15:05 ` 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-58759-4-mXLjs4Cr0H@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).