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/104581] [12 Regression] Huge compile-time regression building SPEC 2017 538.imagick_r with PGO
Date: Fri, 18 Feb 2022 07:50:49 +0000 [thread overview]
Message-ID: <bug-104581-4-hehJpc40IU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104581-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104581
--- Comment #10 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:fe79d652c96b53384ddfa43e312cb0010251391b
commit r12-7293-gfe79d652c96b53384ddfa43e312cb0010251391b
Author: Richard Biener <rguenther@suse.de>
Date: Thu Feb 17 14:40:16 2022 +0100
target/104581 - compile-time regression in mode-switching
The x86 backend piggy-backs on mode-switching for insertion of
vzeroupper. A recent improvement there was implemented in a way
to walk possibly the whole basic-block for all DF reg def definitions
in its mode_needed hook which is called for each instruction in
a basic-block during mode-switching local analysis.
The following mostly reverts this improvement. It needs to be
re-done in a way more consistent with a local dataflow which
probably means making targets aware of the state of the local
dataflow analysis.
2022-02-17 Richard Biener <rguenther@suse.de>
PR target/104581
* config/i386/i386.cc (ix86_avx_u128_mode_source): Remove.
(ix86_avx_u128_mode_needed): Return AVX_U128_DIRTY instead
of calling ix86_avx_u128_mode_source which would eventually
have returned AVX_U128_ANY in some very special case.
* gcc.target/i386/pr101456-1.c: XFAIL.
next prev parent reply other threads:[~2022-02-18 7:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 11:33 [Bug target/104581] New: " rguenth at gcc dot gnu.org
2022-02-17 11:33 ` [Bug target/104581] [12 Regression] " rguenth at gcc dot gnu.org
2022-02-17 11:47 ` rguenth at gcc dot gnu.org
2022-02-17 11:56 ` rguenth at gcc dot gnu.org
2022-02-17 12:35 ` rguenth at gcc dot gnu.org
2022-02-17 12:43 ` rguenth at gcc dot gnu.org
2022-02-17 12:54 ` jakub at gcc dot gnu.org
2022-02-17 12:57 ` rguenth at gcc dot gnu.org
2022-02-17 13:03 ` jakub at gcc dot gnu.org
2022-02-17 13:04 ` jakub at gcc dot gnu.org
2022-02-17 13:11 ` rguenther at suse dot de
2022-02-18 7:50 ` cvs-commit at gcc dot gnu.org [this message]
2022-02-18 7:51 ` rguenth at gcc dot gnu.org
2022-02-18 18:41 ` cvs-commit 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-104581-4-hehJpc40IU@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).