public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/109086] __builtin_strcmp generates wrong code if expand_simple_binop assigns new pseudo-register for result Date: Wed, 15 Mar 2023 09:29:55 +0000 [thread overview] Message-ID: <bug-109086-4-zqKTE2qMHS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109086-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109086 Xi Ruoyao <xry111 at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #13 from Xi Ruoyao <xry111 at gcc dot gnu.org> --- Pushed the patch with a comment explaining the if (result != diff) block.
prev parent reply other threads:[~2023-03-15 9:29 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-10 7:36 [Bug target/109086] New: Bug of builtin_strcmp in the case of using the adddi3 instruction patterns liwei at loongson dot cn 2023-03-10 7:38 ` [Bug target/109086] " liwei at loongson dot cn 2023-03-10 8:18 ` [Bug rtl-optimization/109086] " rguenth at gcc dot gnu.org 2023-03-10 9:31 ` liwei at loongson dot cn 2023-03-10 13:12 ` rguenth at gcc dot gnu.org 2023-03-14 14:59 ` xry111 at gcc dot gnu.org 2023-03-15 2:00 ` xry111 at gcc dot gnu.org 2023-03-15 2:04 ` xry111 at gcc dot gnu.org 2023-03-15 2:17 ` liwei at loongson dot cn 2023-03-15 3:02 ` xry111 at gcc dot gnu.org 2023-03-15 4:52 ` liwei at loongson dot cn 2023-03-15 7:33 ` [Bug other/109086] __builtin_strcmp generates wrong code if expand_simple_binop assigns new pseudo-register for result xry111 at gcc dot gnu.org 2023-03-15 7:36 ` rguenth at gcc dot gnu.org 2023-03-15 9:28 ` cvs-commit at gcc dot gnu.org 2023-03-15 9:29 ` xry111 at gcc dot gnu.org [this message]
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-109086-4-zqKTE2qMHS@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).