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 target/62011] False Data Dependency in popcnt instruction
Date: Wed, 13 Aug 2014 08:23:00 -0000	[thread overview]
Message-ID: <bug-62011-4-ZUh5ODGB4e@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62011-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62011

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-08-13
     Ever confirmed|0                           |1

--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed at least.


  parent reply	other threads:[~2014-08-13  8:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04 14:29 [Bug rtl-optimization/62011] New: " debiandev at gmail dot com
2014-08-05  9:07 ` [Bug target/62011] " rguenth at gcc dot gnu.org
2014-08-05 11:49 ` amonakov at gcc dot gnu.org
2014-08-05 13:40 ` debiandev at gmail dot com
2014-08-07  9:22 ` finis at in dot tum.de
2014-08-11 14:37 ` ysrumyan at gmail dot com
2014-08-12  8:38 ` ysrumyan at gmail dot com
2014-08-12 10:49 ` finis at in dot tum.de
2014-08-12 11:26 ` ysrumyan at gmail dot com
2014-08-13  8:23 ` rguenth at gcc dot gnu.org [this message]
2014-08-21 18:04 ` uros at gcc dot gnu.org
2014-08-21 18:06 ` ubizjak at gmail dot com
2021-10-11 13:46 ` malincns at 163 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-62011-4-ZUh5ODGB4e@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).