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/100809] PPC: __int128 divide/modulo does not use P10 instructions vdivsq/vdivuq
Date: Wed, 14 Jul 2021 17:25:51 +0000 [thread overview]
Message-ID: <bug-100809-4-PvThps39gE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100809-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100809
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Michael Meissner
<meissner@gcc.gnu.org>:
https://gcc.gnu.org/g:8ebcd3608584e544ae8e7c422b3f2400758c47f5
commit r11-8743-g8ebcd3608584e544ae8e7c422b3f2400758c47f5
Author: Michael Meissner <meissner@linux.ibm.com>
Date: Wed Jul 14 13:23:51 2021 -0400
Generate 128-bit int divide/modulus on power10.
This patch adds support for the VDIVSQ, VDIVUQ, VMODSQ, and VMODUQ
instructions to do 128-bit arithmetic.
Backported from master: 2021-07-07 Michael Meissner
<meissner@linux.ibm.com>
2021-07-14 Michael Meissner <meissner@linux.ibm.com>
gcc/
PR target/100809
* config/rs6000/rs6000.md (udivti3): New insn.
(divti3): New insn.
(umodti3): New insn.
(modti3): New insn.
gcc/testsuite/
PR target/100809
* gcc.target/powerpc/p10-vdivq-vmodq.c: New test.
next prev parent reply other threads:[~2021-07-14 17:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 7:58 [Bug c++/100809] New: " jens.seifert at de dot ibm.com
2021-05-28 8:12 ` [Bug c++/100809] " jens.seifert at de dot ibm.com
2021-06-01 14:59 ` wschmidt at gcc dot gnu.org
2021-06-01 22:55 ` meissner at gcc dot gnu.org
2021-06-01 22:58 ` meissner at gcc dot gnu.org
2021-06-04 20:17 ` meissner at gcc dot gnu.org
2021-07-08 1:56 ` [Bug target/100809] " cvs-commit at gcc dot gnu.org
2021-07-14 17:25 ` cvs-commit at gcc dot gnu.org [this message]
2021-07-14 17:53 ` meissner 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-100809-4-PvThps39gE@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).