public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "k.even-mendoza at imperial dot ac.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/100536] ICE: in expand_call with large union (1GB) argument
Date: Mon, 10 Jan 2022 21:27:14 +0000	[thread overview]
Message-ID: <bug-100536-4-9ARQjjRgNz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100536-4@http.gcc.gnu.org/bugzilla/>

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

Karine EM <k.even-mendoza at imperial dot ac.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |k.even-mendoza at imperial dot ac.
                   |                            |uk

--- Comment #5 from Karine EM <k.even-mendoza at imperial dot ac.uk> ---
With GCC-11 and GCC-10, the compiler does not crash but returns: "confused by
earlier errors, bailing out" and ends gracefully. But with GCC-12, I got a
similar crash, with a flat array, a bit over 1GB:

     1  struct a {
     2    char arr[1100000000];
     3  } b[1];
     4  void c(struct a e) {
     5    if (__builtin_memcmp(e.arr, b, 6))
     6      __builtin_abort();
     7  }
     8  int main() {
     9    struct a d;
    10    d.arr;
    11    c(d);
    12    return 0;
    13  }

However, the compiler does recognize the huge stack and gives: "sorry,
unimplemented: passing too large argument on stack", but still crash. If there
is already an error printed, what is the problem to terminate the compilation
gracefully as GCC-11 and GCC-10 used to do?



==========
With GCC-11 and GCC-10 (at least for this case):
gcc-10 -O2 2c8efdb591d9739d4434f1c216106706c62bd78f_v2.c
2c8efdb591d9739d4434f1c216106706c62bd78f_v2.c: In function ‘main’:
2c8efdb591d9739d4434f1c216106706c62bd78f_v2.c:11:3: sorry, unimplemented:
passing too large argument on stack
   11 |   c(d);
      |   ^~~~
2c8efdb591d9739d4434f1c216106706c62bd78f_v2.c:11: confused by earlier errors,
bailing out

==========
With GCC-12 ((GCC) 12.0.0 20211216 (experimental)), this is the trace:
2c8efdb591d9739d4434f1c216106706c62bd78f.c:11:3: sorry, unimplemented: passing
too large argument on stack
   11 |   c(d);
      |   ^~~~
during RTL pass: expand
2c8efdb591d9739d4434f1c216106706c62bd78f.c:11:3: internal compiler error: in
expand_call, at calls.c:3905
0x6cced7 expand_call(tree_node*, rtx_def*, int)
        .././../gcc-source/gcc/calls.c:3905
0xb43a3f expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expand_modifier, rtx_def**, bool)
        .././../gcc-source/gcc/expr.c:11536
0xa14b41 expand_expr
        .././../gcc-source/gcc/expr.h:301
0xa14b41 expand_call_stmt
        .././../gcc-source/gcc/cfgexpand.c:2831
0xa14b41 expand_gimple_stmt_1
        .././../gcc-source/gcc/cfgexpand.c:3864
0xa14b41 expand_gimple_stmt
        .././../gcc-source/gcc/cfgexpand.c:4028
0xa1a67e expand_gimple_basic_block
        .././../gcc-source/gcc/cfgexpand.c:6069
0xa1c527 execute
        .././../gcc-source/gcc/cfgexpand.c:6795
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.

  parent reply	other threads:[~2022-01-10 21:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-11 16:20 [Bug c/100536] New: ICE: in expand_call, at calls.c:4980 cnsun at uwaterloo dot ca
2021-05-11 22:03 ` [Bug middle-end/100536] ICE: in expand_call with large union (1GB) argument pinskia at gcc dot gnu.org
2021-05-12  6:45 ` rguenth at gcc dot gnu.org
2021-05-12 22:56 ` cnsun at uwaterloo dot ca
2021-07-04 18:21 ` pinskia at gcc dot gnu.org
2022-01-10 21:27 ` k.even-mendoza at imperial dot ac.uk [this message]
2022-01-11  1:17 ` pinskia at gcc dot gnu.org
2022-02-28  8:07 ` roger at nextmovesoftware dot com

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-100536-4-9ARQjjRgNz@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).