public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/107762] New: [13 Regression] Recent change causing regressions on s390-linux-gnu Date: Sat, 19 Nov 2022 17:34:47 +0000 [thread overview] Message-ID: <bug-107762-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107762 Bug ID: 107762 Summary: [13 Regression] Recent change causing regressions on s390-linux-gnu Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: law at gcc dot gnu.org CC: ebotcazou at gcc dot gnu.org Target Milestone: --- Target: s390-linux-gnu This change: commit 3e2bdf2460a34a2389dee813a2ba8ecf976f2ec9 Author: Eric Botcazou <ebotcazou@adacore.com> Date: Fri Nov 4 11:15:57 2022 +0100 Do not use subword paradoxical subregs in emit_group_store The goal of the trick is to make life easier for the combiner, but subword paradoxical subregs make it harder for the register allocator instead. gcc/ * expr.cc (emit_group_store): Do not use subword paradoxical subregs Is causing at least two regressions on s390-linux-gnu: Tests that now fail, but worked before (19 tests): [ ... ] gcc.target/s390/arch12/mul-1.c scan-assembler-times \tmsgrkc\t 1 gcc.target/s390/arch13/sel-1.c scan-assembler-times \tselgr(?:h|le)\t 1 [ ... ] Those are the only two that I have positively confirmed are due to the emit_group_store change. I looked briefly at the resulting assembly code for the mul-1 test and it looks worse to me after that change. But I'm far from an s390 expert. You can see this with a cross compiler, you don't need a full toolchain to test.
next reply other threads:[~2022-11-19 17:34 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-19 17:34 law at gcc dot gnu.org [this message] 2022-11-19 19:07 ` [Bug rtl-optimization/107762] " ebotcazou at gcc dot gnu.org 2022-11-22 8:31 ` rguenth at gcc dot gnu.org 2023-02-21 13:45 ` rguenth at gcc dot gnu.org 2023-03-14 8:18 ` jakub at gcc dot gnu.org 2023-03-14 9:38 ` ebotcazou at gcc dot gnu.org 2023-03-14 10:43 ` cvs-commit at gcc dot gnu.org 2023-03-14 10:43 ` ebotcazou at gcc dot gnu.org 2023-03-14 11:35 ` jakub at gcc dot gnu.org 2023-03-14 11:48 ` ebotcazou 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-107762-4@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).