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 rtl-optimization/107762] [13 Regression] Recent change causing regressions on s390-linux-gnu Date: Tue, 14 Mar 2023 10:43:07 +0000 [thread overview] Message-ID: <bug-107762-4-25Nh2SGuXy@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 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Eric Botcazou <ebotcazou@gcc.gnu.org>: https://gcc.gnu.org/g:8b6c38ef6a7a8cc1f7cc2ff86a686e07ceab1641 commit r13-6659-g8b6c38ef6a7a8cc1f7cc2ff86a686e07ceab1641 Author: Eric Botcazou <ebotcazou@adacore.com> Date: Tue Mar 14 10:39:11 2023 +0100 Revert latest change to emit_group_store This pessimizes on targets with insv instructions. gcc/ PR rtl-optimization/107762 * expr.cc (emit_group_store): Revert latest change.
next prev parent reply other threads:[~2023-03-14 10:43 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 ` [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 [this message] 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-25Nh2SGuXy@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).