public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/106064] Wrong code comparing two global zero-sized arrays Date: Fri, 24 Jun 2022 10:28:32 +0000 [thread overview] Message-ID: <bug-106064-4-AkVI2zzwpU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106064-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106064 Alex Coplan <acoplan at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #5 from Alex Coplan <acoplan at gcc dot gnu.org> --- Bisection shows this changed with r9-5411-g93aa3c4aca3647645cd5bce724f9d2126de4b5ea on AArch64: commit 93aa3c4aca3647645cd5bce724f9d2126de4b5ea (refs/bisect/bad) Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Jan 15 09:11:00 2019 +0100 re PR tree-optimization/88775 (Optimize std::string assignment) PR tree-optimization/88775 * match.pd (cmp (convert1?@2 addr@0) (convert2? addr@1)): Optimize equal == 0 equality pointer comparisons some more if compared in integral types and either one points to an automatic var and the other to a global, or we can prove at least one points to the middle or both point to start or both point to end. * gcc.dg/tree-ssa/pr88775-1.c: New test. * gcc.dg/tree-ssa/pr88775-2.c: New test.
next prev parent reply other threads:[~2022-06-24 10:28 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-23 12:36 [Bug tree-optimization/106064] New: " acoplan at gcc dot gnu.org 2022-06-23 16:21 ` [Bug tree-optimization/106064] " ktkachov at gcc dot gnu.org 2022-06-24 9:56 ` mikpelinux at gmail dot com 2022-06-24 10:20 ` pinskia at gcc dot gnu.org 2022-06-24 10:21 ` pinskia at gcc dot gnu.org 2022-06-24 10:28 ` acoplan at gcc dot gnu.org [this message] 2022-06-24 10:30 ` rguenth at gcc dot gnu.org 2022-06-24 10:34 ` acoplan at gcc dot gnu.org 2022-06-24 10:50 ` jakub at gcc dot gnu.org 2022-06-27 10:15 ` acoplan at gcc dot gnu.org 2022-06-27 10:19 ` jakub at gcc dot gnu.org 2022-06-27 12:21 ` acoplan at gcc dot gnu.org 2022-06-27 14:18 ` rearnsha at gcc dot gnu.org 2022-06-27 14:25 ` acoplan at gcc dot gnu.org 2022-07-08 17:02 ` acoplan 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-106064-4-AkVI2zzwpU@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).