public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/45685] GCC optimizer for Intel x64 generates inefficient code Date: Fri, 17 Sep 2010 10:03:00 -0000 [thread overview] Message-ID: <20100917100253.32176.qmail@sourceware.org> (raw) In-Reply-To: <bug-45685-19696@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from ubizjak at gmail dot com 2010-09-17 10:02 ------- Confirmed. Regression? -- ubizjak at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |NEW Ever Confirmed|0 |1 Last reconfirmed|2010-09-17 09:59:36 |2010-09-17 10:02:53 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45685
next prev parent reply other threads:[~2010-09-17 10:03 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-09-16 1:17 [Bug rtl-optimization/45685] New: " ekuznetsov at divxcorp dot com 2010-09-16 1:19 ` [Bug rtl-optimization/45685] " ekuznetsov at divxcorp dot com 2010-09-16 23:09 ` ekuznetsov at divxcorp dot com 2010-09-17 9:59 ` ubizjak at gmail dot com 2010-09-17 10:03 ` ubizjak at gmail dot com [this message] 2010-09-17 13:04 ` [Bug rtl-optimization/45685] [4.6 Regression] " hjl dot tools at gmail dot com 2010-09-17 13:45 ` matz at gcc dot gnu dot 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=20100917100253.32176.qmail@sourceware.org \ --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).