public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90448] [8/9 Regression] decltype-based lambda parameter pack is rejected
Date: Thu, 23 Apr 2020 17:55:07 +0000	[thread overview]
Message-ID: <bug-90448-4-pTPTr3y2bA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-90448-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The testcase ICEs on powerpc64-linux with -m32:
lambda-generic-variadic20.C:5:12: internal compiler error: in
expand_expr_addr_expr_1, at expr.c:8075
    5 |   auto L = [](auto ... a) {
      |            ^~~~~~~~~~~~~~~~
    6 |     auto M = [](decltype(a) ... b) -> void {
      |     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    7 |     };
      |     ~~      
    8 |     return M;
      |     ~~~~~~~~~
    9 |   };
      |   ~         
0xd9422a expand_expr_addr_expr_1
        ../../gcc/expr.c:8075
0xd94817 expand_expr_addr_expr
        ../../gcc/expr.c:8188
0xda0a68 expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expand_modifier, rtx_def**, bool)
        ../../gcc/expr.c:11363
0xd94bcd expand_expr_real(tree_node*, rtx_def*, machine_mode, expand_modifier,
rtx_def**, bool)
        ../../gcc/expr.c:8358
0xc050ff expand_normal
        ../../gcc/expr.h:288
0xc0686f precompute_register_parameters
        ../../gcc/calls.c:982
0xc0fc27 expand_call(tree_node*, rtx_def*, int)
        ../../gcc/calls.c:4398
0xd9f9cb expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expand_modifier, rtx_def**, bool)
        ../../gcc/expr.c:11135
0xd94bcd expand_expr_real(tree_node*, rtx_def*, machine_mode, expand_modifier,
rtx_def**, bool)
        ../../gcc/expr.c:8358
0xd8cef5 store_expr(tree_node*, rtx_def*, int, bool, bool)
        ../../gcc/expr.c:5752
0xd8c194 expand_assignment(tree_node*, tree_node*, bool)
        ../../gcc/expr.c:5514
0xc2860b expand_call_stmt
        ../../gcc/cfgexpand.c:2701
0xc2b6b5 expand_gimple_stmt_1
        ../../gcc/cfgexpand.c:3682
0xc2bc49 expand_gimple_stmt
        ../../gcc/cfgexpand.c:3847
0xc32a16 expand_gimple_basic_block
        ../../gcc/cfgexpand.c:5887
0xc3401a execute
        ../../gcc/cfgexpand.c:6542
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

  parent reply	other threads:[~2020-04-23 17:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-90448-4@http.gcc.gnu.org/bugzilla/>
2020-04-22 14:57 ` [Bug c++/90448] [8/9/10 " paolo.carlini at oracle dot com
2020-04-22 16:05 ` cvs-commit at gcc dot gnu.org
2020-04-23 17:55 ` jakub at gcc dot gnu.org [this message]
2020-04-23 19:30 ` [Bug c++/90448] [8/9 " ro at gcc dot gnu.org
2020-04-24 13:11 ` jakub at gcc dot gnu.org
2020-07-10 13:06 ` [Bug c++/90448] [8/9/10/11 " ro at gcc dot gnu.org
2021-01-20 15:07 ` ro at gcc dot gnu.org
2021-03-04 21:49 ` seurer at gcc dot gnu.org
2021-03-04 21:51 ` seurer at gcc dot gnu.org
2021-03-08 10:22 ` ebotcazou at gcc dot gnu.org
2021-03-09 15:23 ` cvs-commit at gcc dot gnu.org
2021-03-09 15:24 ` cvs-commit at gcc dot gnu.org
2021-03-09 15:25 ` ebotcazou at gcc dot gnu.org
2022-04-01  6:07 ` linkw 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-90448-4-pTPTr3y2bA@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).