public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/65216] [5 Regression] wrong code at -O3 on x86_64-linux-gnu Date: Thu, 26 Feb 2015 05:26:00 -0000 [thread overview] Message-ID: <bug-65216-4-NNxVAaHmRD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65216-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65216 Kai Tietz <ktietz at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |5.0
next prev parent reply other threads:[~2015-02-26 0:09 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-26 1:19 [Bug tree-optimization/65216] New: " su at cs dot ucdavis.edu 2015-02-26 3:15 ` [Bug tree-optimization/65216] " ktietz at gcc dot gnu.org 2015-02-26 3:45 ` glisse at gcc dot gnu.org 2015-02-26 5:26 ` ktietz at gcc dot gnu.org [this message] 2015-02-26 8:39 ` [Bug tree-optimization/65216] [5 Regression] " jakub at gcc dot gnu.org 2015-02-26 10:14 ` rguenth at gcc dot gnu.org 2015-02-26 12:49 ` jakub at gcc dot gnu.org 2015-02-27 0:12 ` jakub at gcc dot gnu.org 2015-02-27 0:25 ` jakub at gcc dot gnu.org 2015-03-04 12:30 ` ktietz 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-65216-4-NNxVAaHmRD@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).