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 tree-optimization/59715] [4.7/4.8/4.9 Regression] wrong code at -Os and above on x86_64-linux-gnu Date: Wed, 08 Jan 2014 12:32:00 -0000 [thread overview] Message-ID: <bug-59715-4-qWJjQuPsPs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59715-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59715 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org --- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> --- Mine then.
next prev parent reply other threads:[~2014-01-08 12:32 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-08 6:37 [Bug tree-optimization/59715] New: " su at cs dot ucdavis.edu 2014-01-08 6:58 ` [Bug tree-optimization/59715] " steven at gcc dot gnu.org 2014-01-08 7:07 ` jakub at gcc dot gnu.org 2014-01-08 7:12 ` [Bug tree-optimization/59715] [4.7/4.8/4.9 Regression] " jakub at gcc dot gnu.org 2014-01-08 9:06 ` steven at gcc dot gnu.org 2014-01-08 11:08 ` vries at gcc dot gnu.org 2014-01-08 11:46 ` rguenth at gcc dot gnu.org 2014-01-08 12:32 ` rguenth at gcc dot gnu.org [this message] 2014-01-08 13:08 ` rguenth at gcc dot gnu.org 2014-01-08 13:54 ` rguenth at gcc dot gnu.org 2014-01-08 14:20 ` rguenth at gcc dot gnu.org 2014-01-09 9:21 ` rguenth at gcc dot gnu.org 2014-01-09 9:30 ` [Bug tree-optimization/59715] [4.7/4.8 " rguenth at gcc dot gnu.org 2014-01-10 8:37 ` rguenth at gcc dot gnu.org 2014-05-07 10:02 ` [Bug tree-optimization/59715] [4.7 " rguenth at gcc dot gnu.org 2014-05-07 10:07 ` 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-59715-4-qWJjQuPsPs@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).