public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/94313] stores into string literals sometimes silently eliminated
Date: Wed, 25 Mar 2020 16:33:57 +0000	[thread overview]
Message-ID: <bug-94313-4-LcObXkzMno@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94313-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
Removing invalid code not isn't wrong (as in non-conforming), but it's
decidedly unhelpful in avoiding the undefined behavior that doesn't necessarily
go away just because the invalid statement is gone.  It makes finding the
underlying bugs difficult.  My solution for pr90404 detects most of these bugs
(and can also eliminate the buggy code) except those that are removed by DSE. 
The intent of this report isn't so much to complain that GCC is doing something
wrong but to document the rationale for doing something different (i.e.,
diagnose these bugs consistently and leave it up to the user whether to
eliminate the code or replace it with a trap or something else).

  parent reply	other threads:[~2020-03-25 16:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-24 21:54 [Bug middle-end/94313] New: " msebor at gcc dot gnu.org
2020-03-25  7:54 ` [Bug middle-end/94313] " rguenth at gcc dot gnu.org
2020-03-25 16:33 ` msebor at gcc dot gnu.org [this message]
2020-03-25 17:49 ` rguenther at suse dot de
2020-03-25 20:08 ` msebor 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-94313-4-LcObXkzMno@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).