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/113408] ICE: in handle_cast, at gimple-lower-bitint.cc:1539 at -O with _BitInt()
Date: Wed, 17 Jan 2024 12:57:44 +0000	[thread overview]
Message-ID: <bug-113408-4-XNo75ASxs5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113408-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113408

--- Comment #3 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:2fb78d431ff3c05997ef31837d6eb319d84a4239

commit r14-8184-g2fb78d431ff3c05997ef31837d6eb319d84a4239
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Wed Jan 17 13:55:50 2024 +0100

    lower-bitint: Fix up VIEW_CONVERT_EXPR handling [PR113408]

    Unlike NOP_EXPR/CONVERT_EXPR which are GIMPLE_UNARY_RHS, VIEW_CONVERT_EXPR
    is GIMPLE_SINGLE_RHS and so gimple_assign_rhs1 contains the operand wrapped
    in VIEW_CONVERT_EXPR tree.

    So, to handle it like other casts we need to look through it.

    2024-01-17  Jakub Jelinek  <jakub@redhat.com>

            PR tree-optimization/113408
            * gimple-lower-bitint.cc (bitint_large_huge::handle_stmt): For
            VIEW_CONVERT_EXPR, pass TREE_OPERAND (rhs1, 0) rather than rhs1
            to handle_cast.

            * gcc.dg/bitint-71.c: New test.

  parent reply	other threads:[~2024-01-17 12:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 20:26 [Bug tree-optimization/113408] New: " zsojka at seznam dot cz
2024-01-16 11:19 ` [Bug tree-optimization/113408] " jakub at gcc dot gnu.org
2024-01-16 11:58 ` jakub at gcc dot gnu.org
2024-01-17 12:57 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-17 12:58 ` jakub at gcc dot gnu.org
2024-01-20 17:10 ` 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-113408-4-XNo75ASxs5@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: link
Be 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).