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/113316] during GIMPLE pass: bitintlower ICE: SIGSEGV in var_to_partition (tree-ssa-live.h:163) at -O with uninitialized _BitInt() function argument Date: Fri, 12 Jan 2024 10:19:50 +0000 [thread overview] Message-ID: <bug-113316-4-osVeSNt1GW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113316-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113316 --- Comment #2 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:c1680bd2df187e06089b06ffe211c4abe4c440b0 commit r14-7179-gc1680bd2df187e06089b06ffe211c4abe4c440b0 Author: Jakub Jelinek <jakub@redhat.com> Date: Fri Jan 12 11:19:08 2024 +0100 lower-bitint: Fix up handling of uninitialized large/huge _BitInt call arguments [PR113316] The code to assign large/huge _BitInt SSA_NAMEs to partitions intentionally ignores uninitialized SSA_NAMEs: /* Also ignore uninitialized uses. */ if (SSA_NAME_IS_DEFAULT_DEF (s) && (!SSA_NAME_VAR (s) || VAR_P (SSA_NAME_VAR (s)))) continue; because there is no need to store them into memory, all we need is when trying to extract some limb from them use uninitialized SSA_NAME for the limb. The following testcase shows this is a problem for call arguments though, for those we need to create replacement SSA_NAMEs which are loaded from the underlying variable. For uninitialized SSA_NAMEs because we didn't create underlying variable for them var_to_partition doesn't work, the following patch handles it by just creating an uninitialized replacement SSA_NAME. 2024-01-12 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/113316 * gimple-lower-bitint.cc (bitint_large_huge::lower_call): Handle uninitialized large/huge _BitInt arguments to calls. * gcc.dg/bitint-67.c: New test.
next prev parent reply other threads:[~2024-01-12 10:19 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-10 21:19 [Bug tree-optimization/113316] New: " zsojka at seznam dot cz 2024-01-11 13:05 ` [Bug tree-optimization/113316] " jakub at gcc dot gnu.org 2024-01-12 10:19 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-12 10:27 ` jakub at gcc dot gnu.org 2024-01-20 17:08 ` 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-113316-4-osVeSNt1GW@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).