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++/99456] [11 regression] ABI breakage with some static initialization
Date: Fri, 19 Mar 2021 17:38:02 +0000	[thread overview]
Message-ID: <bug-99456-4-3nkav4Hm9D@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99456-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:82bb66730bc42b8694fdebef607ea6e49e8496bf

commit r11-7740-g82bb66730bc42b8694fdebef607ea6e49e8496bf
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Mar 19 18:36:56 2021 +0100

    c++: Only reject reinterpret casts from pointers to integers for
manifestly_const_eval evaluation [PR99456]

    My PR82304/PR95307 fix moved reinterpret cast from pointer to integer
    diagnostics from cxx_eval_outermost_constant_expr where it caught
    invalid code only at the outermost level down into
    cxx_eval_constant_expression.
    Unfortunately, it regressed following testcase, we emit worse code
    including dynamic initialization of some vars.
    While the initializers are not constant expressions due to the
    reinterpret_cast in there, there is no reason not to fold them as an
    optimization.

    I've tried to make this dependent on !ctx->quiet, but that regressed
    two further tests, and on ctx->strict, which regressed other tests,
    so this patch bases that on manifestly_const_eval.

    The new testcase is now optimized as much as it used to be in GCC 10
    and the only regression it causes is an extra -Wnarrowing warning
    on vla22.C test on invalid code (which the patch adjusts).

    2021-03-19  Jakub Jelinek  <jakub@redhat.com>

            PR c++/99456
            * constexpr.c (cxx_eval_constant_expression): For CONVERT_EXPR from
            INDIRECT_TYPE_P to ARITHMETIC_TYPE_P, when
!ctx->manifestly_const_eval
            don't diagnose it, set *non_constant_p nor return t.

            * g++.dg/opt/pr99456.C: New test.
            * g++.dg/ext/vla22.C: Expect a -Wnarrowing warning for c++11 and
            later.

  parent reply	other threads:[~2021-03-19 17:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-07 20:50 [Bug c++/99456] New: " nathan at gcc dot gnu.org
2021-03-07 20:51 ` [Bug c++/99456] " nathan at gcc dot gnu.org
2021-03-07 20:51 ` nathan at gcc dot gnu.org
2021-03-07 21:01 ` pinskia at gcc dot gnu.org
2021-03-08  9:56 ` rguenth at gcc dot gnu.org
2021-03-08 11:34 ` jakub at gcc dot gnu.org
2021-03-08 12:47 ` nathan at gcc dot gnu.org
2021-03-08 13:21 ` jakub at gcc dot gnu.org
2021-03-08 13:30 ` jakub at gcc dot gnu.org
2021-03-08 13:32 ` nathan at gcc dot gnu.org
2021-03-08 13:39 ` jakub at gcc dot gnu.org
2021-03-08 14:03 ` jakub at gcc dot gnu.org
2021-03-08 14:21 ` jakub at gcc dot gnu.org
2021-03-08 15:48 ` nathan at gcc dot gnu.org
2021-03-09 10:12 ` jakub at gcc dot gnu.org
2021-03-09 11:05 ` jakub at gcc dot gnu.org
2021-03-19 17:38 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-19 17:38 ` jakub at gcc dot gnu.org
2021-03-22  2:09 ` unlvsur at live dot com

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-99456-4-3nkav4Hm9D@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).