public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rdapp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/106919] [13 Regression] RTL check: expected code 'set' or 'clobber', have 'if_then_else' in s390_rtx_costs, at config/s390/s390.cc:3672on s390x-linux-gnu since r13-2251-g1930c5d05ceff2 Date: Fri, 23 Sep 2022 08:44:03 +0000 [thread overview] Message-ID: <bug-106919-4-VzUtlgLjuz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106919-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106919 --- Comment #8 from rdapp at gcc dot gnu.org --- Yes, one of dst and dest is superflous. Looks good like that. I bootstrapped the same patch locally already, no regressions.
next prev parent reply other threads:[~2022-09-23 8:44 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-12 23:32 [Bug target/106919] New: [13 Regression] RTL check: expected code 'set' or 'clobber', have 'if_then_else' in s390_rtx_costs, at config/s390/s390.cc:3672on s390x-linux-gnu doko at gcc dot gnu.org 2022-09-13 6:49 ` [Bug target/106919] " rguenth at gcc dot gnu.org 2022-09-13 11:27 ` marxin at gcc dot gnu.org 2022-09-22 9:47 ` doko at gcc dot gnu.org 2022-09-22 9:48 ` doko at gcc dot gnu.org 2022-09-22 9:50 ` doko at gcc dot gnu.org 2022-09-22 19:35 ` marxin at gcc dot gnu.org 2022-09-22 20:07 ` [Bug target/106919] [13 Regression] RTL check: expected code 'set' or 'clobber', have 'if_then_else' in s390_rtx_costs, at config/s390/s390.cc:3672on s390x-linux-gnu since r13-2251-g1930c5d05ceff2 marxin at gcc dot gnu.org 2022-09-22 20:12 ` marxin at gcc dot gnu.org 2022-09-23 8:44 ` rdapp at gcc dot gnu.org [this message] 2022-09-26 10:09 ` marxin 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-106919-4-VzUtlgLjuz@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).