public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113102] during GIMPLE pass: bitintlower ICE: SIGSEGV with _BitInt() at -O1 or -O2 Date: Fri, 22 Dec 2023 11:30:29 +0000 [thread overview] Message-ID: <bug-113102-4-H4Y7X8YUj0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113102-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113102 --- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:f5198f0264e773d3b5d55f09a579313b0b231527 commit r14-6804-gf5198f0264e773d3b5d55f09a579313b0b231527 Author: Jakub Jelinek <jakub@redhat.com> Date: Fri Dec 22 12:28:06 2023 +0100 lower-bitint: Handle unreleased SSA_NAMEs from earlier passes gracefully [PR113102] On the following testcase earlier passes leave around an unreleased SSA_NAME - non-GIMPLE_NOP SSA_NAME_DEF_STMT which isn't in any bb. The following patch makes bitint lowering resistent against those, the first hunk is where we'd for certain kinds of stmts try to ammend them and the latter is where we'd otherwise try to remove them, neither of which works. The other loops over all SSA_NAMEs either already also check gimple_bb (SSA_NAME_DEF_STMT (s)) or it doesn't matter that much if we process it or not (worst case it means e.g. the pass wouldn't return early even when it otherwise could). 2023-12-22 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/113102 * gimple-lower-bitint.cc (gimple_lower_bitint): Handle unreleased large/huge _BitInt SSA_NAMEs. * gcc.dg/bitint-59.c: New test.
next prev parent reply other threads:[~2023-12-22 11:30 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-21 7:07 [Bug tree-optimization/113102] New: " zsojka at seznam dot cz 2023-12-21 7:08 ` [Bug tree-optimization/113102] " zsojka at seznam dot cz 2023-12-21 14:18 ` jakub at gcc dot gnu.org 2023-12-21 14:18 ` jakub at gcc dot gnu.org 2023-12-22 11:30 ` cvs-commit at gcc dot gnu.org 2023-12-22 11:30 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-17 13:47 ` jakub at gcc dot gnu.org 2024-01-20 17:11 ` pinskia 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-113102-4-H4Y7X8YUj0@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).