public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "muecker at gwdg dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/103770] [11 Regression] ICE related to VLA
Date: Wed, 29 Dec 2021 12:10:44 +0000	[thread overview]
Message-ID: <bug-103770-4-owNRCj7HUh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103770-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Martin Uecker <muecker at gwdg dot de> ---
Here is another example which fails on armel


extern _Complex float g(int N, int dims[N]);

void f(void)
{
        int dims[1];
        _Complex float val = g(1, dims);
}

during RTL pass: expand
BUG.c: In function 'f':
BUG.c:10:30: internal compiler error: Segmentation fault
   10 |         _Complex float val = g(1, dims);
      |                              ^~~~~~~~~~

0xb1393f crash_signal
        ../../src/gcc/toplev.c:327
0x708398 get_size_range(range_query*, tree_node*, gimple*, tree_node**, int)
        ../../src/gcc/calls.c:1274
0x70c4d4 get_size_range(range_query*, tree_node*, gimple*, tree_node**, int)
        ../../src/gcc/calls.c:1266
0x70c4d4 get_size_range(tree_node*, tree_node**, int)
        ../../src/gcc/calls.c:1401
0x70c4d4 maybe_warn_rdwr_sizes
        ../../src/gcc/calls.c:2034
0x70dcb1 initialize_argument_information
        ../../src/gcc/calls.c:2626
0x70dcb1 expand_call(tree_node*, rtx_def*, int)
        ../../src/gcc/calls.c:4010
0x8210ce expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expand_modifier, rtx_def**, bool)
        ../../src/gcc/expr.c:11287
0x82a9ce expand_expr_real(tree_node*, rtx_def*, machine_mode, expand_modifier,
rtx_def**, bool)
        ../../src/gcc/expr.c:8519
0x82a9ce store_expr(tree_node*, rtx_def*, int, bool, bool)
        ../../src/gcc/expr.c:5886
0x82be69 expand_assignment(tree_node*, tree_node*, bool)
        ../../src/gcc/expr.c:5622
0x720bf9 expand_call_stmt
        ../../src/gcc/cfgexpand.c:2838
0x720bf9 expand_gimple_stmt_1
        ../../src/gcc/cfgexpand.c:3871
0x720bf9 expand_gimple_stmt
        ../../src/gcc/cfgexpand.c:4035
0x726b97 expand_gimple_basic_block
        ../../src/gcc/cfgexpand.c:6077
0x726b97 execute
        ../../src/gcc/cfgexpand.c:6761
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <file:///usr/share/doc/gcc-11/README.Bugs> for instructions.


arm-linux-gnueabi-gcc (Debian 11.2.0-9) 11.2.0
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

  parent reply	other threads:[~2021-12-29 12:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-19 18:30 [Bug c/103770] New: " muecker at gwdg dot de
2021-12-19 21:17 ` [Bug middle-end/103770] [11 Regression] " pinskia at gcc dot gnu.org
2021-12-20  9:09 ` marxin at gcc dot gnu.org
2021-12-20 11:48 ` pinskia at gcc dot gnu.org
2021-12-29 12:10 ` muecker at gwdg dot de [this message]
2021-12-29 20:20 ` pinskia at gcc dot gnu.org
2022-03-26 21:42 ` pinskia at gcc dot gnu.org
2022-04-21  7:51 ` rguenth at gcc dot gnu.org
2023-01-28 18:15 ` muecker at gwdg dot de
2023-05-29 10:06 ` jakub 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-103770-4-owNRCj7HUh@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).