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/99881] Regression compare -O2 -ftree-vectorize with -O2 on SKX/CLX
Date: Tue, 22 Feb 2022 07:59:09 +0000 [thread overview]
Message-ID: <bug-99881-4-KiZW12riiI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99881-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99881
--- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:90d693bdc9d71841f51d68826ffa5bd685d7f0bc
commit r12-7319-g90d693bdc9d71841f51d68826ffa5bd685d7f0bc
Author: Richard Biener <rguenther@suse.de>
Date: Fri Feb 18 14:32:14 2022 +0100
target/99881 - x86 vector cost of CTOR from integer regs
This uses the now passed SLP node to the vectorizer costing hook
to adjust vector construction costs for the cost of moving an
integer component from a GPR to a vector register when that's
required for building a vector from components. A cruical difference
here is whether the component is loaded from memory or extracted
from a vector register as in those cases no intermediate GPR is involved.
The pr99881.c testcase can be Un-XFAILed with this patch, the
pr91446.c testcase now produces scalar code which looks superior
to me so I've adjusted it as well.
2022-02-18 Richard Biener <rguenther@suse.de>
PR tree-optimization/104582
PR target/99881
* config/i386/i386.cc (ix86_vector_costs::add_stmt_cost):
Cost GPR to vector register moves for integer vector construction.
* gcc.dg/vect/costmodel/x86_64/costmodel-pr104582-1.c: New.
* gcc.dg/vect/costmodel/x86_64/costmodel-pr104582-2.c: Likewise.
* gcc.dg/vect/costmodel/x86_64/costmodel-pr104582-3.c: Likewise.
* gcc.dg/vect/costmodel/x86_64/costmodel-pr104582-4.c: Likewise.
* gcc.target/i386/pr99881.c: Un-XFAIL.
* gcc.target/i386/pr91446.c: Adjust to not expect vectorization.
next prev parent reply other threads:[~2022-02-22 7:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 3:49 [Bug target/99881] New: " crazylht at gmail dot com
2021-04-02 14:29 ` [Bug target/99881] " hjl.tools at gmail dot com
2021-04-02 19:34 ` hjl.tools at gmail dot com
2021-04-06 7:48 ` rguenth at gcc dot gnu.org
2021-04-06 10:06 ` crazylht at gmail dot com
2021-04-06 11:44 ` rguenth at gcc dot gnu.org
2021-07-28 2:48 ` cvs-commit at gcc dot gnu.org
2021-07-28 2:49 ` crazylht at gmail dot com
2021-07-28 22:47 ` jakub at gcc dot gnu.org
2021-07-29 1:09 ` crazylht at gmail dot com
2021-07-29 2:18 ` cvs-commit at gcc dot gnu.org
2021-08-19 2:32 ` crazylht at gmail dot com
2022-02-22 7:59 ` cvs-commit at gcc dot gnu.org [this message]
2022-02-22 8:00 ` rguenth 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-99881-4-KiZW12riiI@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).