public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cnsun at uwaterloo dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/102759] New: ICE: Segmentation fault, contains_struct_check(tree_node*, tree_node_structure_enum, char const*, int,  char const*), maybe_check_access_sizes
Date: Fri, 15 Oct 2021 02:44:46 +0000	[thread overview]
Message-ID: <bug-102759-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 102759
           Summary: ICE: Segmentation fault,
                    contains_struct_check(tree_node*,
                    tree_node_structure_enum, char const*, int, char
                    const*), maybe_check_access_sizes
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: cnsun at uwaterloo dot ca
  Target Milestone: ---

This might be a duplicate to PR 100784

$ gcc-trunk -v
Using built-in specs.
COLLECT_GCC=gcc-trunk
COLLECT_LTO_WRAPPER=/scratch/software/gcc-trunk/libexec/gcc/x86_64-pc-linux-gnu/12.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /tmp/tmp.gzh6IUhxke-gcc-builder/gcc/configure
--enable-languages=c,c++,lto --enable-checking-yes --enable-multiarch
--prefix=/scratch/software/gcc-trunk --disable-bootstrap
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 12.0.0 20211014 (experimental) [master -gee9fa8a57] (GCC)

$ cat mutant.c
a4() { void fa4(int[]); }
void fa4();
call_fa4() { fa4(a4); }

$ gcc-trunk -w mutant.c
during GIMPLE pass: waccess
mutant.c: In function ‘call_fa4’:
mutant.c:3:1: internal compiler error: Segmentation fault
    3 | call_fa4() { fa4(a4); }
      | ^~~~~~~~
0xf8c8d3 crash_signal
        /tmp/tmp.gzh6IUhxke-gcc-builder/gcc/gcc/toplev.c:326
0x72b653 contains_struct_check(tree_node*, tree_node_structure_enum, char
const*, int, char const*)
        /tmp/tmp.gzh6IUhxke-gcc-builder/gcc/gcc/tree.h:3546
0x72b653 maybe_check_access_sizes
        /tmp/tmp.gzh6IUhxke-gcc-builder/gcc/gcc/gimple-ssa-warn-access.cc:2880
0xc822f4 check_call
        /tmp/tmp.gzh6IUhxke-gcc-builder/gcc/gcc/gimple-ssa-warn-access.cc:3151
0xc822f4 check
        /tmp/tmp.gzh6IUhxke-gcc-builder/gcc/gcc/gimple-ssa-warn-access.cc:3310
0xc822f4 check
        /tmp/tmp.gzh6IUhxke-gcc-builder/gcc/gcc/gimple-ssa-warn-access.cc:3326
0xc822f4 execute
        /tmp/tmp.gzh6IUhxke-gcc-builder/gcc/gcc/gimple-ssa-warn-access.cc:3340
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.

             reply	other threads:[~2021-10-15  2:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15  2:44 cnsun at uwaterloo dot ca [this message]
2021-10-15  2:54 ` [Bug ipa/102759] [12 Regression] ICE: Segmentation fault in maybe_check_access_sizes pinskia at gcc dot gnu.org
2021-10-15  8:19 ` [Bug tree-optimization/102759] [12 Regression] ICE: Segmentation fault in maybe_check_access_sizes since r12-2976-gb48d4e6818674898 marxin at gcc dot gnu.org
2021-10-15 14:35 ` msebor at gcc dot gnu.org
2021-11-05 13:59 ` rguenth at gcc dot gnu.org
2021-11-15 20:33 ` msebor at gcc dot gnu.org
2021-11-17 22:10 ` cvs-commit at gcc dot gnu.org
2021-11-17 22:11 ` msebor 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-102759-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).