public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55966] __atomic_fetch_* generate wrong code for HLE
Date: Mon, 14 Jan 2013 22:23:00 -0000 [thread overview]
Message-ID: <bug-55966-4-aNJUTSZtWe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55966-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55966
Andrew Macleod <amacleod at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amacleod at redhat dot com
--- Comment #7 from Andrew Macleod <amacleod at redhat dot com> 2013-01-14 22:22:58 UTC ---
What do you mean 'forbid' it?
Isn't the HLE bit suppose to be a hint anyway? Saying if the hardware supports
it, use it on this atomic instruction... Its not incorrect to ignore it, and
some targets simply don't support it. so its ignored.
I would expect that when we have to drop back to a compare-exchange loop we're
no longer going to really care?
next prev parent reply other threads:[~2013-01-14 22:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 6:11 [Bug target/55966] New: " andi-gcc at firstfloor dot org
2013-01-14 19:06 ` [Bug target/55966] " andi-gcc at firstfloor dot org
2013-01-14 19:52 ` andi-gcc at firstfloor dot org
2013-01-14 20:15 ` andi-gcc at firstfloor dot org
2013-01-14 21:22 ` ubizjak at gmail dot com
2013-01-14 21:25 ` ubizjak at gmail dot com
2013-01-14 22:05 ` andi-gcc at firstfloor dot org
2013-01-14 22:23 ` amacleod at redhat dot com [this message]
2013-01-14 22:32 ` andi-gcc at firstfloor dot org
2013-01-14 22:34 ` andi-gcc at firstfloor dot org
2024-04-09 2:58 ` pinskia 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-55966-4-aNJUTSZtWe@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).