public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/107762] [13 Regression] Recent change causing regressions on s390-linux-gnu
Date: Sat, 19 Nov 2022 19:07:56 +0000 [thread overview]
Message-ID: <bug-107762-4-LCxTXNDZNe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107762-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107762
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2022-11-19
Ever confirmed|0 |1
Assignee|unassigned at gcc dot gnu.org |ebotcazou at gcc dot gnu.org
--- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> 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.
Thanks for the heads up, I'll have a quick look.
next prev parent reply other threads:[~2022-11-19 19:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 17:34 [Bug rtl-optimization/107762] New: " law at gcc dot gnu.org
2022-11-19 19:07 ` ebotcazou at gcc dot gnu.org [this message]
2022-11-22 8:31 ` [Bug rtl-optimization/107762] " 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-LCxTXNDZNe@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).