public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/102560] [12 Regression] g++.dg/Walloca1.C ICE with aggressive GC Date: Sat, 02 Oct 2021 16:48:11 +0000 [thread overview] Message-ID: <bug-102560-4-nGYvpngU7S@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102560-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102560 --- Comment #2 from Aldy Hernandez <aldyh at gcc dot gnu.org> --- Going up the backtrace we see: (gdb) #3 0x0000000001b43aff in irange::intersect (this=0x7fffffffc8e0, other=0x3c7aa40 <alloca_call_type(gimple*, bool)::invalid_range>) at /home/aldyh/src/gcc/gcc/value-range.cc:1514 (gdb) #4 0x0000000001b3e1e8 in irange::intersect (this=0x7fffffffc8e0, r=...) at /home/aldyh/src/gcc/gcc/value-range.h:549 (gdb) #5 0x0000000002a78c33 in alloca_call_type (stmt=<gimple_call 0x7fffea151240>, is_vla=false) at /home/aldyh/src/gcc/gcc/gimple-ssa-warn-alloca.c:229 We're intersecting with invalid_range which is a static member: static int_range<2> invalid_range (build_int_cst (size_type_node, 0), build_int_cst (size_type_node, max_size), VR_ANTI_RANGE); It looks like it has members that have been GC freed: (gdb) print invalid_range $9 = {<irange> = {m_num_ranges = 1 '\001', m_max_ranges = 2 '\002', m_kind = VR_RANGE, m_base = 0x3c7aa50 <alloca_call_type(gimple*, bool)::invalid_range+16>}, m_ranges = { <ggc_freed 0x7fffea157b88>, <integer_cst 0x7fffe9fe2620>, <tree 0x0>, <tree 0x0>}} (gdb) The m_ranges bits are trees in int_range<N>, which live in GC, and trees are inherently GC'ish.
next prev parent reply other threads:[~2021-10-02 16:48 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-02 0:59 [Bug tree-optimization/102560] New: " jason at gcc dot gnu.org 2021-10-02 14:12 ` [Bug tree-optimization/102560] " pinskia at gcc dot gnu.org 2021-10-02 16:35 ` aldyh at gcc dot gnu.org 2021-10-02 16:48 ` aldyh at gcc dot gnu.org [this message] 2021-10-02 19:53 ` aldyh at gcc dot gnu.org 2021-10-03 17:51 ` aldyh at gcc dot gnu.org 2021-10-04 6:59 ` rguenth at gcc dot gnu.org 2021-10-04 6:59 ` rguenth at gcc dot gnu.org 2021-10-04 7:02 ` aldyh at gcc dot gnu.org 2021-10-04 11:20 ` cvs-commit at gcc dot gnu.org 2021-10-04 11:21 ` aldyh 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-102560-4-nGYvpngU7S@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: linkBe 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).