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 middle-end/110832] [14 Regression] 14% capacita -O2 regression between g:9fdbd7d6fa5e0a76 (2023-07-26 01:45) and g:ca912a39cccdd990 (2023-07-27 03:44) on zen3 and core Date: Tue, 08 Aug 2023 16:56:33 +0000 [thread overview] Message-ID: <bug-110832-4-ggxUH6Sq88@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110832-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110832 --- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Uros Bizjak <uros@gcc.gnu.org>: https://gcc.gnu.org/g:ad5b757d99b5a121198b79a6a42c1f15ae86a190 commit r14-3085-gad5b757d99b5a121198b79a6a42c1f15ae86a190 Author: Uros Bizjak <ubizjak@gmail.com> Date: Tue Aug 8 18:53:51 2023 +0200 i386: Do not sanitize upper part of V2SFmode reg with -fno-trapping-math [PR110832] Also introduce -m[no-]partial-vector-fp-math option to disable trapping V2SF named patterns in order to avoid generation of partial vector V4SFmode trapping instructions. The new option is enabled by default, because even with sanitization, a small but consistent speed up of 2 to 3% with Polyhedron capacita benchmark can be achieved vs. scalar code. Using -fno-trapping-math improves Polyhedron capacita runtime 8 to 9% vs. scalar code. This is what clang does by default, as it defaults to -fno-trapping-math. PR target/110832 gcc/ChangeLog: * config/i386/i386.opt (mpartial-vector-fp-math): New option. * config/i386/mmx.md (movq_<mode>_to_sse): Do not sanitize upper part of V2SFmode register with -fno-trapping-math. (<plusminusmult:insn>v2sf3): Enable for ix86_partial_vec_fp_math. (divv2sf3): Ditto. (<smaxmin:code>v2sf3): Ditto. (sqrtv2sf2): Ditto. (*mmx_haddv2sf3_low): Ditto. (*mmx_hsubv2sf3_low): Ditto. (vec_addsubv2sf3): Ditto. (vec_cmpv2sfv2si): Ditto. (vcond<V2FI:mode>v2sf): Ditto. (fmav2sf4): Ditto. (fmsv2sf4): Ditto. (fnmav2sf4): Ditto. (fnmsv2sf4): Ditto. (fix_truncv2sfv2si2): Ditto. (fixuns_truncv2sfv2si2): Ditto. (floatv2siv2sf2): Ditto. (floatunsv2siv2sf2): Ditto. (nearbyintv2sf2): Ditto. (rintv2sf2): Ditto. (lrintv2sfv2si2): Ditto. (ceilv2sf2): Ditto. (lceilv2sfv2si2): Ditto. (floorv2sf2): Ditto. (lfloorv2sfv2si2): Ditto. (btruncv2sf2): Ditto. (roundv2sf2): Ditto. (lroundv2sfv2si2): Ditto. * doc/invoke.texi (x86 Options): Document -mpartial-vector-fp-math option. gcc/testsuite/ChangeLog: * gcc.target/i386/pr110832-1.c: New test. * gcc.target/i386/pr110832-2.c: New test. * gcc.target/i386/pr110832-3.c: New test.
next prev parent reply other threads:[~2023-08-08 16:56 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-27 17:27 [Bug middle-end/110832] New: " hubicka at gcc dot gnu.org 2023-07-27 17:28 ` [Bug middle-end/110832] " hubicka at gcc dot gnu.org 2023-07-27 18:35 ` hubicka at ucw dot cz 2023-07-28 6:21 ` rguenth at gcc dot gnu.org 2023-07-28 6:21 ` [Bug middle-end/110832] [14 Regression] " rguenth at gcc dot gnu.org 2023-07-28 12:30 ` ubizjak at gmail dot com 2023-07-28 12:36 ` ubizjak at gmail dot com 2023-07-28 13:28 ` rguenth at gcc dot gnu.org 2023-07-28 13:41 ` ubizjak at gmail dot com 2023-07-28 15:46 ` ubizjak at gmail dot com 2023-07-31 4:58 ` crazylht at gmail dot com 2023-07-31 7:54 ` ubizjak at gmail dot com 2023-08-08 16:56 ` cvs-commit at gcc dot gnu.org [this message] 2023-08-09 9:46 ` ubizjak at gmail dot com 2023-08-10 6:06 ` cvs-commit at gcc dot gnu.org 2023-08-25 8:59 ` ubizjak at gmail dot com
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-110832-4-ggxUH6Sq88@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: linkBe 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).