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++/111529] [11/12/13 Regression] ICE on bool conversion in an unrolled loop condition inside template lambda nested in another template scope
Date: Fri, 24 May 2024 18:38:25 +0000	[thread overview]
Message-ID: <bug-111529-4-TR928HKkOL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111529-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:

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

commit r11-11448-ga644775c363979bc25951532819ffa0f244b82f4
Author: Jason Merrill <jason@redhat.com>
Date:   Fri Sep 22 12:10:11 2023 +0100

    c++: unroll pragma in templates [PR111529]

    We were failing to handle ANNOTATE_EXPR in tsubst_copy_and_build, leading
to
    problems with substitution of any wrapped expressions.

    Let's also not tell users that lambda templates are available in C++14.

            PR c++/111529

    gcc/cp/ChangeLog:

            * parser.c (cp_parser_lambda_declarator_opt): Don't suggest
            -std=c++14 for lambda templates.
            * pt.c (tsubst_expr): Move ANNOTATE_EXPR handling...
            (tsubst_copy_and_build): ...here.

    gcc/testsuite/ChangeLog:

            * g++.dg/ext/unroll-4.C: New test.

    (cherry picked from commit 9c62af101e11e1cce573c2b3d2e18b403412dbc8)

  parent reply	other threads:[~2024-05-24 18:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-21 21:53 [Bug c++/111529] New: " bugreport0 at proton dot me
2023-09-21 22:00 ` [Bug c++/111529] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org
2023-09-21 22:09 ` bugreport0 at proton dot me
2023-09-21 22:12 ` pinskia at gcc dot gnu.org
2023-09-21 22:15 ` pinskia at gcc dot gnu.org
2023-09-22 13:01 ` cvs-commit at gcc dot gnu.org
2024-05-08 12:16 ` [Bug c++/111529] [11/12/13 " rguenth at gcc dot gnu.org
2024-05-24 13:25 ` cvs-commit at gcc dot gnu.org
2024-05-24 13:26 ` cvs-commit at gcc dot gnu.org
2024-05-24 18:38 ` cvs-commit at gcc dot gnu.org [this message]
2024-05-24 18:41 ` 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-111529-4-TR928HKkOL@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).