public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/111519] [13/14 Regression] Wrong code at -O3 on x86_64-linux-gnu since r13-455-g1fe04c497d Date: Tue, 10 Oct 2023 08:26:17 +0000 [thread overview] Message-ID: <bug-111519-4-uGPiSx8X1t@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111519-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111519 --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- Reverting @@ -5089,8 +5123,9 @@ strlen_pass::handle_store (bool *zero_write) return false; } - if (storing_all_zeros_p - || storing_nonzero_p + if (storing_nonzero_p + || storing_all_zeros_p + || (full_string_p && lenrange[1] == 0) || (offset != 0 && store_before_nul[1] > 0)) { /* When STORING_NONZERO_P, we know that the string will start fixes the issue. We somehow compute a lenrange of { 0, 0, 1 } for d = _8 but also set storing_all_zeros_p to false. It seems that strlen_pass::count_nonzero_bytes happily skips intermediate stores when it handles SSA names here: gimple *stmt = SSA_NAME_DEF_STMT (exp); if (gimple_assign_single_p (stmt)) { exp = gimple_assign_rhs1 (stmt); if (!DECL_P (exp) && TREE_CODE (exp) != CONSTRUCTOR && TREE_CODE (exp) != MEM_REF) return false; /* Handle DECLs, CONSTRUCTOR and MEM_REF below. */ we have _8 = *_7; ... *_7 = prephitmp_89; d = _8; when we recursively process a memory reference we need to verify there are no intermediate aliases, the simplest thing would be to pass down a virtual use. Trying some prototype.
next prev parent reply other threads:[~2023-10-10 8:26 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-21 13:20 [Bug tree-optimization/111519] New: " shaohua.li at inf dot ethz.ch 2023-09-21 15:35 ` [Bug tree-optimization/111519] " pinskia at gcc dot gnu.org 2023-09-21 15:47 ` pinskia at gcc dot gnu.org 2023-09-21 16:00 ` rguenth at gcc dot gnu.org 2023-10-09 22:05 ` roger at nextmovesoftware dot com 2023-10-10 7:56 ` rguenth at gcc dot gnu.org 2023-10-10 8:21 ` jakub at gcc dot gnu.org 2023-10-10 8:26 ` rguenth at gcc dot gnu.org [this message] 2023-10-10 8:31 ` rguenth at gcc dot gnu.org 2023-10-10 8:33 ` rguenth at gcc dot gnu.org 2023-10-10 10:37 ` rguenth at gcc dot gnu.org 2023-10-11 7:09 ` cvs-commit at gcc dot gnu.org 2023-10-11 7:23 ` cvs-commit at gcc dot gnu.org 2023-10-11 7:24 ` jakub at gcc dot gnu.org 2023-11-02 9:05 ` pinskia 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-111519-4-uGPiSx8X1t@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).