public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/94622] testsuite/gcc.dg/atomic/c11-atomic-exec-1.c fails on powerpc64le with -mpcrel
Date: Wed, 22 Apr 2020 17:20:14 +0000 [thread overview]
Message-ID: <bug-94622-4-xETaYOfNdX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94622-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94622
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Aaron Sawdey <acsawdey@gcc.gnu.org>:
https://gcc.gnu.org/g:3bcdb5dec72b6d7b197821c2b814bc9fc07f4628
commit r10-7889-g3bcdb5dec72b6d7b197821c2b814bc9fc07f4628
Author: Aaron Sawdey <acsawdey@linux.ibm.com>
Date: Mon Apr 20 13:01:43 2020 -0500
Use plq/pstq for atomic_{load,store}<mode>
For future architecture with prefix instructions, always use plq/pstq
rather than lq/stq for atomic load of quadword. Then we never have to
do the doubleword swap on little endian. Before this fix, -mno-pcrel
would generate lq with the doubleword swap (which was ok) and -mpcrel
would generate plq, also with the doubleword swap, which was wrong.
2020-04-20 Aaron Sawdey <acsawdey@linux.ibm.com>
PR target/94622
* config/rs6000/sync.md (load_quadpti): Add attr "prefixed"
if TARGET_PREFIXED.
(store_quadpti): Ditto.
(atomic_load<mode>): Do not swap doublewords if TARGET_PREFIXED as
plq will be used and doesn't need it.
(atomic_store<mode>): Ditto, for pstq.
next prev parent reply other threads:[~2020-04-22 17:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 15:48 [Bug target/94622] New: " acsawdey at gcc dot gnu.org
2020-04-16 16:27 ` [Bug target/94622] " acsawdey at gcc dot gnu.org
2020-04-17 22:26 ` acsawdey at gcc dot gnu.org
2020-04-20 17:56 ` acsawdey at gcc dot gnu.org
2020-04-21 21:16 ` acsawdey at gcc dot gnu.org
2020-04-22 17:20 ` cvs-commit at gcc dot gnu.org [this message]
2020-04-22 21:47 ` acsawdey 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-94622-4-xETaYOfNdX@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).