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++/115358] [13/14/15 Regression] template argument deduction/substitution failed in generic lambda function use of static constexpr array type whos initializer defines the size since r13-2540
Date: Fri, 28 Jun 2024 21:14:34 +0000	[thread overview]
Message-ID: <bug-115358-4-9VLazglUKv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115358-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-14 branch has been updated by Patrick Palka
<ppalka@gcc.gnu.org>:

https://gcc.gnu.org/g:33a9c4dd5fcac7e3f5d835b35fe787126339dd2b

commit r14-10357-g33a9c4dd5fcac7e3f5d835b35fe787126339dd2b
Author: Patrick Palka <ppalka@redhat.com>
Date:   Tue Jun 25 10:42:21 2024 -0400

    c++: using non-dep array var of unknown bound [PR115358]

    For a non-dependent array variable of unknown bound, it seems we need to
    try instantiating its definition upon use in a template context for sake
    of proper checking and typing of the overall expression, like we do for
    function specializations with deduced return type.

            PR c++/115358

    gcc/cp/ChangeLog:

            * decl2.cc (mark_used): Call maybe_instantiate_decl for an array
            variable with unknown bound.
            * semantics.cc (finish_decltype_type): Remove now redundant
            handling of array variables with unknown bound.
            * typeck.cc (cxx_sizeof_expr): Likewise.

    gcc/testsuite/ChangeLog:

            * g++.dg/template/array37.C: New test.

    Reviewed-by: Jason Merrill <jason@redhat.com>
    (cherry picked from commit e3915c1ad56591cbd68229a64c941c38330abd69)

  parent reply	other threads:[~2024-06-28 21:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 12:32 [Bug c++/115358] New: template argument deduction/substitution failed on lambda function dongkyun.s at samsung dot com
2024-06-05 12:35 ` [Bug c++/115358] " dongkyun.s at samsung dot com
2024-06-05 12:36 ` dongkyun.s at samsung dot com
2024-06-05 12:53 ` redi at gcc dot gnu.org
2024-06-05 13:12 ` [Bug c++/115358] [13/14/15 Regression] template argument deduction/substitution failed in generic " pinskia at gcc dot gnu.org
2024-06-05 13:19 ` pinskia at gcc dot gnu.org
2024-06-06  6:30 ` [Bug c++/115358] [13/14/15 Regression] template argument deduction/substitution failed in generic lambda function use of static constexpr array type whos initializer defines the size rguenth at gcc dot gnu.org
2024-06-17 11:41 ` [Bug c++/115358] [13/14/15 Regression] template argument deduction/substitution failed in generic lambda function use of static constexpr array type whos initializer defines the size since r13-2540 jakub at gcc dot gnu.org
2024-06-18 17:44 ` ppalka at gcc dot gnu.org
2024-06-25 14:42 ` cvs-commit at gcc dot gnu.org
2024-06-28 21:14 ` cvs-commit at gcc dot gnu.org [this message]
2024-06-28 21:15 ` [Bug c++/115358] [13 " 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-115358-4-9VLazglUKv@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).