public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/115152] [13/14/15 Regression] wrong code at -O3 with "-fno-tree-fre -fno-tree-dominator-opts -fno-tree-loop-im" on x86_64-linux-gnu
Date: Sat, 18 May 2024 21:53:04 +0000	[thread overview]
Message-ID: <bug-115152-4-lrmNe9hqz6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115152-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115152

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The bug is in strlen1:
```
maybe_invalidate called for MEM[(char *)&e] = vect_pretmp_76.13_77;
maybe_invalidate returns 1
maybe_invalidate called for MEM[(char *)&e] = vect_pretmp_89.18_79;
maybe_invalidate returns 1
Optimizing: pretmp_34 = e[0];
into: pretmp_34 = 0;
maybe_invalidate called for e[0] = pretmp_34;
  statement may clobber object &e 0 bytes in size
maybe_invalidate returns 1
maybe_invalidate called for c = _5;
maybe_invalidate returns 0
maybe_invalidate called for a = _54;
maybe_invalidate returns 0
maybe_invalidate called for b = 2;
maybe_invalidate returns 0
maybe_invalidate called for __builtin_abort ();
maybe_invalidate returns 0
pointer_query counters:
  index cache size:   0
  index entries:      0
  access cache size:  0
  access entries:     0
  hits:               0
  misses:             0
  failures:           0
  max_depth:          0
```

  parent reply	other threads:[~2024-05-18 21:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-18 20:22 [Bug tree-optimization/115152] New: " zhendong.su at inf dot ethz.ch
2024-05-18 21:40 ` [Bug tree-optimization/115152] [13/14/15 Regression] " pinskia at gcc dot gnu.org
2024-05-18 21:40 ` pinskia at gcc dot gnu.org
2024-05-18 21:53 ` pinskia at gcc dot gnu.org [this message]
2024-05-18 21:54 ` pinskia at gcc dot gnu.org
2024-05-20 18:27 ` [Bug tree-optimization/115152] [13/14/15 Regression] wrong code at -O3 with "-fno-tree-fre -fno-tree-dominator-opts -fno-tree-loop-im" on x86_64-linux-gnu since r13-455 jakub at gcc dot gnu.org
2024-05-20 18:36 ` jakub at gcc dot gnu.org
2024-05-21  6:38 ` rguenth at gcc dot gnu.org
2024-05-21  9:20 ` jakub at gcc dot gnu.org
2024-05-21 11:57 ` jakub at gcc dot gnu.org
2024-05-22  7:14 ` cvs-commit at gcc dot gnu.org
2024-05-22  7:19 ` cvs-commit at gcc dot gnu.org
2024-05-22  7:35 ` cvs-commit at gcc dot gnu.org
2024-05-22 11:11 ` jakub 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-115152-4-lrmNe9hqz6@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: link
Be 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).