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/113783] ICE: in lower_stmt, at gimple-lower-bitint.cc:5455 with -O -mavx512f and _BitInt() in memcpy() Date: Wed, 07 Feb 2024 11:20:50 +0000 [thread overview] Message-ID: <bug-113783-4-06re1egFRz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113783-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113783 --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Ugh, folding turns this into uint256_t D.3758; <bb 2> : D.3758 = MEM <uint256_t> [(char * {ref-all})&x]; MEM <uint256_t> [(char * {ref-all})p] = D.3758; and later ssa turns it into uint256_t _2; <bb 2> : _2 = VIEW_CONVERT_EXPR<uint256_t>(x_1(D)); MEM <uint256_t> [(char * {ref-all})p_4(D)] = _2; where presumably uint256_t is some 256-bit unsigned INTEGER_TYPE. Except it isn't really supported except perhaps for moves. Similarly void bar (void *p, _BitInt(502) x) { __builtin_memcpy (p, &x, sizeof x); } into uint512_t D.3758; D.3758 = MEM <uint512_t> [(char * {ref-all})&x]; MEM <uint512_t> [(char * {ref-all})p] = D.3758; and later uint512_t _2; <bb 2> : _2 = VIEW_CONVERT_EXPR<uint512_t>(x_1(D)); MEM <uint512_t> [(char * {ref-all})p_4(D)] = _2; I don't see how I could handle that in bitint lowering when shifts, BIT_IOR_EXPR etc. will not work on such types.
next prev parent reply other threads:[~2024-02-07 11:20 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-06 11:13 [Bug tree-optimization/113783] New: " zsojka at seznam dot cz 2024-02-07 11:20 ` jakub at gcc dot gnu.org [this message] 2024-02-07 11:32 ` [Bug tree-optimization/113783] " jakub at gcc dot gnu.org 2024-02-08 12:28 ` jakub at gcc dot gnu.org 2024-02-09 15:17 ` cvs-commit at gcc dot gnu.org 2024-02-09 15:18 ` jakub at gcc dot gnu.org 2024-02-15 8:49 ` 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-113783-4-06re1egFRz@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).