public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "stefansf at linux dot ibm.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/102720] [12 regression] gcc.dg/tree-ssa/ldist-strlen-1.c and ldist-strlen-2.c fail after r12-4324 Date: Wed, 13 Oct 2021 10:14:28 +0000 [thread overview] Message-ID: <bug-102720-4-3ASKIYI6lM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102720-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102720 Stefan Schulze Frielinghaus <stefansf at linux dot ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stefansf at linux dot ibm.com --- Comment #4 from Stefan Schulze Frielinghaus <stefansf at linux dot ibm.com> --- typedef __SIZE_TYPE__ size_t; extern void* malloc (size_t); extern void* memset (void*, int, size_t); __attribute__((noinline)) int test (char *s) { int i; for (i=0; s[i]; ++i); return i; } int main (void) { char *p = malloc (1024); memset (p, 0xf, 1024); // removed p[1] = 0; // removed int i = test (p); if (i != 1) __builtin_abort (); return 0; } $ gcc -O2 -fdump-tree-dse2-details test.c In dse2 we then have: Deleted dead store: MEM[(char *)p_3 + 1B] = 0; Deleted dead call: memset (p_3, 15, 1024); prior g:008e7397dad971c03c08fc1b0a4a98fddccaaed8 the store and call is not removed.
next prev parent reply other threads:[~2021-10-13 10:14 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-12 21:45 [Bug testsuite/102720] New: [12 regression] gcc.dg/tree-ssa/ldist-strlen-1.c and ldist-strlen-2.c fail after r12-4234 seurer at gcc dot gnu.org 2021-10-13 2:16 ` [Bug testsuite/102720] " msebor at gcc dot gnu.org 2021-10-13 7:37 ` rguenth at gcc dot gnu.org 2021-10-13 7:38 ` [Bug tree-optimization/102720] [12 regression] gcc.dg/tree-ssa/ldist-strlen-1.c and ldist-strlen-2.c fail after r12-4324 rguenth at gcc dot gnu.org 2021-10-13 10:14 ` stefansf at linux dot ibm.com [this message] 2021-10-13 14:50 ` clyon at gcc dot gnu.org 2021-10-13 14:52 ` clyon at gcc dot gnu.org 2021-10-15 11:36 ` [Bug ipa/102720] " hubicka at gcc dot gnu.org 2021-10-15 12:21 ` hubicka at gcc dot gnu.org 2021-10-15 13:26 ` hubicka at gcc dot gnu.org 2021-10-15 13:28 ` hubicka at gcc dot gnu.org 2021-10-15 13:54 ` hubicka at gcc dot gnu.org 2021-10-16 12:45 ` [Bug tree-optimization/102720] " cvs-commit at gcc dot gnu.org 2021-11-21 11:57 ` hubicka 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-102720-4-3ASKIYI6lM@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).