public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth 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: Thu, 17 Feb 2022 12:43:19 +0000 [thread overview] Message-ID: <bug-104581-4-oT1etdfBKR@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 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |hjl.tools at gmail dot com Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- For just the special-case of AVX loads from constant zero this is a quite expensive thing to do. diff --git a/gcc/config/i386/i386.cc b/gcc/config/i386/i386.cc index cf246e74e57..e4b42fbba6f 100644 --- a/gcc/config/i386/i386.cc +++ b/gcc/config/i386/i386.cc @@ -14520,11 +14452,7 @@ ix86_avx_u128_mode_needed (rtx_insn *insn) { FOR_EACH_SUBRTX (iter, array, src, NONCONST) if (ix86_check_avx_upper_register (*iter)) - { - int status = ix86_avx_u128_mode_source (insn, *iter); - if (status == AVX_U128_DIRTY) - return status; - } + return AVX_U128_DIRTY; } /* This isn't YMM/ZMM load/store. */ fixes this and makes the compile finish in 16s.
next prev parent reply other threads:[~2022-02-17 12:43 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 [this message] 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 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-oT1etdfBKR@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).