From: Segher Boessenkool <segher@kernel.crashing.org>
To: Pat Haugen <pthaugen@linux.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
"Kewen.Lin" <linkw@linux.ibm.com>,
Peter Bergner <bergner@linux.ibm.com>,
David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH V4, rs6000] Disable generation of scalar modulo instructions
Date: Wed, 13 Sep 2023 15:48:44 -0500 [thread overview]
Message-ID: <20230913204844.GM19790@gate.crashing.org> (raw)
In-Reply-To: <57a342c8-c3ae-b12b-f73a-9dc428acc91e@linux.ibm.com>
Hi!
On Fri, Jun 30, 2023 at 02:26:35PM -0500, Pat Haugen wrote:
> gcc/
> * config/rs6000/rs6000.cc (rs6000_rtx_costs): Check if disabling
> scalar modulo.
"Check whether the modulo instruction is disabled?"
> * config/rs6000/rs6000.md (mod<mode>3, *mod<mode>3): Disable.
> (define_expand umod<mode>3): New.
> (define_insn umod<mode>3): Rename to *umod<mode>3 and disable.
> (umodti3, modti3): Disable.
None of these patterns are disabled! Instead, the new TARGET_* thing
is used.
> +/* Disable generation of scalar modulo instructions due to performance issues
> + with certain input values. This can be removed in the future when the
> + issues have been resolved. */
> +#define RS6000_DISABLE_SCALAR_MODULO 1
I think that is a bit optimistic -- in the future we will still want to
support older cores ;-)
> - "TARGET_POWER10 && TARGET_POWERPC64"
> + "TARGET_POWER10 && TARGET_POWERPC64 && !RS6000_DISABLE_SCALAR_MODULO"
> "vmoduq %0,%1,%2"
Did we ever test if this insn in fact is slower as well? I don't mean
either way, orthogonality is good, but just for my enlightenment.
> +++ b/gcc/testsuite/gcc.target/powerpc/clone1.c
> +/* { Fail due to RS6000_DISABLE_SCALAR_MODULO. */
Xfail, but heh. No need to change that.
> +/* { dg-final { scan-assembler-times {\mdivd\M} 1 { xfail *-*-* } } } */
> +/* { Fail due to RS6000_DISABLE_SCALAR_MODULO. */
> +/* { dg-final { scan-assembler-times {\mmodsw\M} 1 { xfail *-*-* } } } */
Thanks for the \m \M, it is much harder to determine if the tests
actually work, without that :-)
With improved changelog: okay for trunk. Okay for all backports as
well (after some soak time).
Thank you!
Segher
next prev parent reply other threads:[~2023-09-13 20:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 19:26 Pat Haugen
2023-07-13 20:17 ` Pat Haugen
2023-08-01 19:19 ` PING ^2: " Pat Haugen
2023-08-09 18:33 ` PING^3: " Pat Haugen
2023-09-08 15:44 ` PING^4: " Pat Haugen
2023-09-13 20:48 ` Segher Boessenkool [this message]
2023-09-19 20:09 ` Pat Haugen
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=20230913204844.GM19790@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linkw@linux.ibm.com \
--cc=pthaugen@linux.ibm.com \
/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).