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 20:08:54 +0000	[thread overview]
Message-ID: <bug-94313-4-o45KWlivXf@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 #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
An implementation is free to do whatever it wants when it finds
invalid/undefined code.  A quality implementation will also let the user know
about it so it can be fixed.  An even better one will let the user choose what
to do in response (as we discussed in Manchester, it could either trap,
substitute zero, or simply remove the code and proceed as if it was never
there; other alternatives might be possible).  This is all perfectly compatible
with your preference.  As long as the code is diagnosed it also meets my goal.

      parent reply	other threads:[~2020-03-25 20:08 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
2020-03-25 17:49 ` rguenther at suse dot de
2020-03-25 20:08 ` msebor at gcc dot gnu.org [this message]

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-o45KWlivXf@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).