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++/99287] std::source_location::function_name breaks constexpr
Date: Sat, 06 Mar 2021 22:10:30 +0000	[thread overview]
Message-ID: <bug-99287-4-1J2NmXqaBQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99287-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>:

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

commit r11-7546-gd1bba463bd0d5692b7fa58ee37a61a55b2517456
Author: Patrick Palka <ppalka@redhat.com>
Date:   Sat Mar 6 17:09:07 2021 -0500

    c++: Fix constexpr evaluation of pre-increment when !lval [PR99287]

    Here, during cxx_eval_increment_expression (with lval=false) of
    ++__first where __first is &"mystr"[0], we correctly update __first
    to &"mystr"[1] but we end up returning &"mystr"[0] + 1 instead of
    &"mystr"[1].  This unreduced return value inhibits other pointer
    arithmetic folding during later constexpr evaluation, which ultimately
    causes the constexpr evaluation to fail.

    It turns out the simplification of &"mystr"[0] + 1 to &"mystr"[1]
    is performed by cxx_fold_pointer_plus_expression, not by fold_build2.
    So we perform this simplification during constexpr evaluation of
    the temporary MODIFY_EXPR (during which we assign to __first the
    simplified value), but then we return 'mod' which has only been folded
    via fold_build2 and hasn't gone through cxx_fold_pointer_plus_expression.

    This patch fixes this by updating 'mod' with the result of the
    MODIFY_EXPR evaluation appropriately, so that it captures any additional
    folding of the expression when !lval.  We now need to be wary of this
    evaluation failing and returning e.g. the MODIFY_EXPR or NULL_TREE; it
    seems checking *non_constant_p should cover our bases here and is
    generally prudent.

    gcc/cp/ChangeLog:

            PR c++/99287
            * constexpr.c (cxx_eval_increment_expression): Pass lval when
            evaluating the MODIFY_EXPR, and update 'mod' with the result of
            this evaluation.  Check *non_constant_p afterwards.  For prefix
            ops, just return 'mod'.

    gcc/testsuite/ChangeLog:

            PR c++/99287
            * g++.dg/cpp2a/constexpr-99287.C: New test.

    Co-authored-by: Jakub Jelinek <jakub@redhat.com>

  parent reply	other threads:[~2021-03-06 22:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-26 12:29 [Bug c++/99287] New: " nickgray0 at brown dot edu
2021-02-26 15:46 ` [Bug c++/99287] " jakub at gcc dot gnu.org
2021-02-26 15:49 ` jakub at gcc dot gnu.org
2021-03-05 15:30 ` ppalka at gcc dot gnu.org
2021-03-05 15:39 ` jakub at gcc dot gnu.org
2021-03-05 15:57 ` jakub at gcc dot gnu.org
2021-03-05 16:08 ` ppalka at gcc dot gnu.org
2021-03-06 22:10 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-06 22:12 ` ppalka 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-99287-4-1J2NmXqaBQ@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).