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/55845] 454.calculix miscompares with -march=btver2 -O3 -ffastmath -fschedule-insns -mvzeroupper for test data run
Date: Wed, 02 Jan 2013 10:10:00 -0000	[thread overview]
Message-ID: <bug-55845-4-aasvmOU5El@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55845-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55845

Uros Bizjak <ubizjak at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vbyakovl23 at gmail dot com

--- Comment #1 from Uros Bizjak <ubizjak at gmail dot com> 2013-01-02 10:10:01 UTC ---
Adding CC.


  reply	other threads:[~2013-01-02 10:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-02  9:28 [Bug rtl-optimization/55845] New: " venkataramanan.kumar at amd dot com
2013-01-02 10:10 ` ubizjak at gmail dot com [this message]
2013-01-02 10:15 ` [Bug rtl-optimization/55845] " ubizjak at gmail dot com
2013-01-04  6:41 ` vbyakovl23 at gmail dot com
2013-01-04  8:13 ` ubizjak at gmail dot com
2013-01-04  9:12 ` venkataramanan.kumar at amd dot com
2013-01-04  9:20 ` ubizjak at gmail dot com
2013-01-04  9:25 ` venkataramanan.kumar at amd dot com
2013-01-04  9:35 ` [Bug rtl-optimization/55845] [4.8 Regression] " ubizjak at gmail dot com
2013-01-06 13:24 ` ubizjak at gmail dot com
2013-01-06 15:51 ` ubizjak at gmail dot com
2013-01-07 15:46 ` rguenth at gcc dot gnu.org
2013-01-08 18:01 ` jakub at gcc dot gnu.org
2013-01-08 18:04 ` jakub at gcc dot gnu.org
2013-01-15 14:05 ` venkataramanan.kumar at amd dot com

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-55845-4-aasvmOU5El@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: link
Be 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).