public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/106099] [13 Regression] ICE in execute_todo, at passes.cc:2134 since r13-1204-gd68d366425369649 Date: Mon, 04 Jul 2022 11:38:41 +0000 [thread overview] Message-ID: <bug-106099-4-s6v1tUUlLK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106099-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106099 --- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> --- And there is another thing, we need to check all these gimple_build_builtin_unreachable and builtin_decl_unreachable and build_builtin_unreachable calls and check if any of them aren't done during IPA with the assumed new caller not being set as cfun. Because those functions test flag_* etc. vars and if there would be such calls, we'd need to pass struct function * and use opts_for_fn instead of flag_*.
next prev parent reply other threads:[~2022-07-04 11:38 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-27 6:52 [Bug tree-optimization/106099] New: ICE in execute_todo, at passes.cc:2134 asolokha at gmx dot com 2022-06-27 9:04 ` [Bug tree-optimization/106099] " zsojka at seznam dot cz 2022-06-27 9:07 ` [Bug tree-optimization/106099] [13 Regression] ICE in execute_todo, at passes.cc:2134 since r13-1204-gd68d366425369649 marxin at gcc dot gnu.org 2022-06-27 9:18 ` pinskia at gcc dot gnu.org 2022-06-27 10:48 ` rguenth at gcc dot gnu.org 2022-07-04 10:10 ` marxin at gcc dot gnu.org 2022-07-04 10:12 ` marxin at gcc dot gnu.org 2022-07-04 11:35 ` jakub at gcc dot gnu.org 2022-07-04 11:38 ` jakub at gcc dot gnu.org [this message] 2022-07-26 10:25 ` jakub at gcc dot gnu.org 2022-07-28 10:43 ` cvs-commit at gcc dot gnu.org 2022-07-30 8:22 ` zsojka at seznam dot cz 2022-08-26 7:29 ` cvs-commit at gcc dot gnu.org 2022-10-18 13:02 ` jakub at gcc dot gnu.org 2023-01-03 11:23 ` 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-106099-4-s6v1tUUlLK@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).