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 tree-optimization/80794] constant objects can be assumed to be immutable
Date: Mon, 14 Sep 2020 15:57:41 +0000	[thread overview]
Message-ID: <bug-80794-4-WfL6VwwCYD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-80794-4@http.gcc.gnu.org/bugzilla/>

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

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=90404,
                   |                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=86318

--- Comment #9 from Martin Sebor <msebor at gcc dot gnu.org> ---
See also pr86318 and especially pr90404.  As noted in c#2 on the former,
issuing a warning when an attempt is detected to modify a const object (or
subobject) as requested in pr90404 should help detect changes, resulting from
the optimization, to the behavior of code that deliberately violates the
restriction to modify constant subobjects.

  parent reply	other threads:[~2020-09-14 15:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-80794-4@http.gcc.gnu.org/bugzilla/>
2020-09-14 15:18 ` msebor at gcc dot gnu.org
2020-09-14 15:57 ` msebor at gcc dot gnu.org [this message]
2020-09-14 16:18 ` matthijs at stdin dot nl

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-80794-4-WfL6VwwCYD@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).