public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/107317] New: [10/11/12/13 Regression] ICE in emit_redzone_byte, at asan.cc:1508
Date: Wed, 19 Oct 2022 17:29:08 +0000	[thread overview]
Message-ID: <bug-107317-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107317
           Summary: [10/11/12/13 Regression] ICE in emit_redzone_byte, at
                    asan.cc:1508
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Started with r10 between 20190512 and 20190519,
with option -m32 and -fopenmp or -frecursive :


$ cat z1.f90
program p
   real :: a(1000000, 100, 2)
   call s(a(:, 1:200, :))
end


$ gfortran-13-20221016 -c z1.f90 -m32 -O2 -fsanitize=address -frecursive
z1.f90:3:15:

    3 |    call s(a(:, 1:200, :))
      |               1
Warning: Upper array reference at (1) is out of bounds (200 > 100) in dimension
2
z1.f90:1:9:

    1 | program p
      |         ^
Error: total size of local objects 2400000512 exceeds maximum 2147483392
during RTL pass: expand
z1.f90:1:9: internal compiler error: in emit_redzone_byte, at asan.cc:1508
0xf5c70e asan_redzone_buffer::emit_redzone_byte(long, unsigned char)
        ../../gcc/asan.cc:1508
0xf64786 asan_emit_stack_protection(rtx_def*, rtx_def*, unsigned int, long*,
tree_node**, int)
        ../../gcc/asan.cc:2003
0x9d9ba2 expand_used_vars
        ../../gcc/cfgexpand.cc:2376
0x9de182 execute
        ../../gcc/cfgexpand.cc:6664

             reply	other threads:[~2022-10-19 17:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 17:29 gscfq@t-online.de [this message]
2022-10-20  8:41 ` [Bug fortran/107317] " marxin at gcc dot gnu.org
2022-10-20  9:15 ` rguenth at gcc dot gnu.org
2022-10-20 18:51 ` anlauf at gcc dot gnu.org
2022-10-20 20:05 ` tkoenig at gcc dot gnu.org
2022-10-22  8:36 ` tkoenig at gcc dot gnu.org
2022-11-23 12:48 ` jakub at gcc dot gnu.org
2022-11-23 12:51 ` jakub at gcc dot gnu.org
2022-11-23 16:52 ` [Bug middle-end/107317] " jakub at gcc dot gnu.org
2022-11-24 10:30 ` cvs-commit at gcc dot gnu.org
2022-11-24 10:31 ` [Bug middle-end/107317] [10/11/12 " jakub at gcc dot gnu.org
2023-02-10 17:44 ` cvs-commit at gcc dot gnu.org
2023-02-10 17:57 ` [Bug middle-end/107317] [10/11 " jakub at gcc dot gnu.org
2023-05-02 20:12 ` cvs-commit at gcc dot gnu.org
2023-05-03  9:30 ` [Bug middle-end/107317] [10 " jakub at gcc dot gnu.org
2023-05-03 15:19 ` cvs-commit at gcc dot gnu.org
2023-05-04  7:21 ` 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-107317-4@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).