public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91529] [8/9/10/11 Regression] -fmerge-all-constants leads to corrupt output without inlining
Date: Fri, 01 May 2020 17:59:10 +0000	[thread overview]
Message-ID: <bug-91529-4-dd7gBDK6Ea@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91529-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>:

https://gcc.gnu.org/g:a2f32550a085984fbaaec962bf7723514ac71dff

commit r11-16-ga2f32550a085984fbaaec962bf7723514ac71dff
Author: Jason Merrill <jason@redhat.com>
Date:   Fri May 1 13:53:32 2020 -0400

    c++: -fmerge-all-constants vs. destructors [PR91529]

    cp_finish_decl avoids setting TREE_READONLY on TREE_STATIC variables that
    have non-constant construction or destruction, but -fmerge-all-constants
was
    converting an automatic variable to static while leaving TREE_READONLY set.

    Fixed by clearing the flag in cp_finish_decl in the presence of
    -fmerge-all-constants.

    gcc/cp/ChangeLog
    2020-05-01  Jason Merrill  <jason@redhat.com>

            PR c++/91529
            * decl.c (cp_finish_decl): Also clear TREE_READONLY if
            -fmerge-all-constants.

  parent reply	other threads:[~2020-05-01 17:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-91529-4@http.gcc.gnu.org/bugzilla/>
2020-04-30 18:59 ` jason at gcc dot gnu.org
2020-05-01 17:59 ` cvs-commit at gcc dot gnu.org [this message]
2020-05-25 22:05 ` cvs-commit at gcc dot gnu.org
2020-05-25 22:38 ` cvs-commit at gcc dot gnu.org
2020-05-25 22:45 ` cvs-commit at gcc dot gnu.org
2020-05-25 22:47 ` jason 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-91529-4-dd7gBDK6Ea@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).