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/113692] ICE: in lower_stmt, at gimple-lower-bitint.cc:5444 at -O with _BitInt() in a condition Date: Fri, 02 Feb 2024 10:30:23 +0000 [thread overview] Message-ID: <bug-113692-4-84CJqhvChW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113692-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113692 --- Comment #6 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:fb28d5cdae149f08f0d472c210a5143a64771410 commit r14-8747-gfb28d5cdae149f08f0d472c210a5143a64771410 Author: Jakub Jelinek <jakub@redhat.com> Date: Fri Feb 2 11:28:31 2024 +0100 lower-bitint: Handle casts from large/huge _BitInt to pointer/reference types [PR113692] I thought one needs to cast first to pointer-sized integer before casting to pointer, but apparently that is not the case. So the following patch arranges for the large/huge _BitInt to pointer/reference conversions to use the same code as for conversions of them to small integral types. 2024-02-02 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/113692 * gimple-lower-bitint.cc (bitint_large_huge::lower_stmt): Handle casts from large/huge BITINT_TYPEs to POINTER_TYPE/REFERENCE_TYPE as final_cast_p. * gcc.dg/bitint-82.c: New test.
next prev parent reply other threads:[~2024-02-02 10:30 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-31 21:20 [Bug tree-optimization/113692] New: " zsojka at seznam dot cz 2024-01-31 21:25 ` [Bug tree-optimization/113692] " pinskia at gcc dot gnu.org 2024-01-31 21:50 ` pinskia at gcc dot gnu.org 2024-02-01 7:48 ` rguenth at gcc dot gnu.org 2024-02-01 11:03 ` jakub at gcc dot gnu.org 2024-02-01 11:30 ` jakub at gcc dot gnu.org 2024-02-02 10:30 ` cvs-commit at gcc dot gnu.org [this message] 2024-02-02 10:34 ` 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-113692-4-84CJqhvChW@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).