public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/102474] [12 regression] Crash in ipa-modref compiling Go code Date: Tue, 28 Sep 2021 23:24:29 +0000 [thread overview] Message-ID: <bug-102474-4-qzKmblDljC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102474-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102474 --- Comment #2 from Ian Lance Taylor <ian at airs dot com> --- I did a git bisect, and it reported that the problem was introduced by commit f5ff3a8ed4ca91737c16757ce4938cf2e0187fc0 Author: Jan Hubicka <hubicka@ucw.cz> Date: Sat Aug 28 20:57:08 2021 +0200 Improve handling of table overflows in modref_ref_node gcc/ChangeLog: * ipa-modref-tree.h (modref_access_node::merge): Break out logic combining offsets and logic merging ranges to ... (modref_access_node::combined_offsets): ... here (modref_access_node::update2): ... here (modref_access_node::closer_pair_p): New member function. (modref_access_node::forced_merge): New member function. (modre_ref_node::insert): Do merging when table is full. gcc/testsuite/ChangeLog: * gcc.dg/tree-ssa/modref-9.c: New test.
next prev parent reply other threads:[~2021-09-28 23:24 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-23 20:34 [Bug tree-optimization/102474] New: " ian at airs dot com 2021-09-24 0:40 ` [Bug tree-optimization/102474] " pinskia at gcc dot gnu.org 2021-09-24 0:42 ` [Bug ipa/102474] " pinskia at gcc dot gnu.org 2021-09-24 6:53 ` rguenth at gcc dot gnu.org 2021-09-27 12:38 ` marxin at gcc dot gnu.org 2021-09-28 23:24 ` ian at airs dot com [this message] 2021-09-30 11:55 ` marxin at gcc dot gnu.org 2021-10-06 14:57 ` hubicka at gcc dot gnu.org 2021-10-07 18:50 ` ian at airs 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-102474-4-qzKmblDljC@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).