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++/111132] [11/12/13/14 Regression] Function redeclaration in local scope breaks constant expression evaluation
Date: Fri, 05 Apr 2024 13:11:16 +0000	[thread overview]
Message-ID: <bug-111132-4-qmhrsqmc2a@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111132-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>:

https://gcc.gnu.org/g:8c9063825ce726fcbbc067d8a6d062cc2d4acf5e

commit r14-9809-g8c9063825ce726fcbbc067d8a6d062cc2d4acf5e
Author: Marek Polacek <polacek@redhat.com>
Date:   Tue Apr 2 12:59:38 2024 -0400

    c++: constexpr error with fn redecl in local scope [PR111132]

    We evaluate constexpr functions on the original, pre-genericization bodies.
    That means that the function body we're evaluating will not have gone
    through cp_genericize_r's "Map block scope extern declarations to visible
    declarations with the same name and type in outer scopes if any".  Here:

      constexpr bool bar() { return true; } // #1
      constexpr bool foo() {
        constexpr bool bar(void); // #2
        return bar();
      }

    it means that we:
    1) register_constexpr_fundef (#1)
    2) cp_genericize (#1)
       nothing interesting happens
    3) register_constexpr_fundef (foo)
       does copy_fn, so we have two copies of the BIND_EXPR
    4) cp_genericize (foo)
       this remaps #2 to #1, but only on one copy of the BIND_EXPR
    5) retrieve_constexpr_fundef (foo)
       we find it, no problem
    6) retrieve_constexpr_fundef (#2)
       and here #2 isn't found in constexpr_fundef_table, because
       we're working on the BIND_EXPR copy where #2 wasn't mapped to #1
       so we fail.  We've only registered #1.

    It should work to use DECL_LOCAL_DECL_ALIAS (which used to be
    extern_decl_map).  We evaluate constexpr functions on pre-cp_fold
    bodies to avoid diagnostic problems, but the remapping I'm proposing
    should not interfere with diagnostics.

    This is not a problem for a global scope redeclaration; there we go
    through duplicate_decls which keeps the DECL_UID:
      DECL_UID (olddecl) = olddecl_uid;
    and DECL_UID is what constexpr_fundef_hasher::hash uses.

            PR c++/111132

    gcc/cp/ChangeLog:

            * constexpr.cc (get_function_named_in_call): Use
            cp_get_fndecl_from_callee.
            * cvt.cc (cp_get_fndecl_from_callee): If there's a
            DECL_LOCAL_DECL_ALIAS, use it.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp0x/constexpr-redeclaration3.C: New test.
            * g++.dg/cpp0x/constexpr-redeclaration4.C: New test.

  parent reply	other threads:[~2024-04-05 13:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24 12:54 [Bug c++/111132] New: " fchelnokov at gmail dot com
2023-08-24 18:29 ` [Bug c++/111132] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org
2023-08-24 19:54 ` ppalka at gcc dot gnu.org
2023-10-17 10:27 ` rguenth at gcc dot gnu.org
2024-03-07 23:23 ` law at gcc dot gnu.org
2024-04-01 23:18 ` mpolacek at gcc dot gnu.org
2024-04-05 13:11 ` cvs-commit at gcc dot gnu.org [this message]
2024-04-05 13:26 ` [Bug c++/111132] [11/12/13 " mpolacek 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-111132-4-qmhrsqmc2a@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).