public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ville.voutilainen at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/66881] Possibly inefficient std::atomic<int> codegen on x86 for simple arithmetic
Date: Wed, 15 Jul 2015 16:29:00 -0000 [thread overview]
Message-ID: <bug-66881-4-vltMDEtAGl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66881-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66881
--- Comment #2 from Ville Voutilainen <ville.voutilainen at gmail dot com> ---
(In reply to H.J. Lu from comment #1)
> Dup of PR 50677?
Well, this report has no volatiles in it, so perhaps not?
next prev parent reply other threads:[~2015-07-15 16:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 16:05 [Bug middle-end/66881] New: " tkoeppe at google dot com
2015-07-15 16:23 ` [Bug middle-end/66881] " hjl.tools at gmail dot com
2015-07-15 16:29 ` ville.voutilainen at gmail dot com [this message]
2015-07-15 16:30 ` hjl.tools at gmail dot com
2015-07-15 16:37 ` hjl.tools at gmail dot com
2015-07-15 16:37 ` hjl.tools at gmail dot com
2015-07-20 21:57 ` jfb at chromium 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=bug-66881-4-vltMDEtAGl@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).