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/113330] ICE: verify_gimple failed: conversion of register to a different size in 'view_convert_expr' with -O -fstack-check=generic and _BitInt()
Date: Fri, 12 Jan 2024 10:22:41 +0000	[thread overview]
Message-ID: <bug-113330-4-aqEOiST3ac@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113330-4@http.gcc.gnu.org/bugzilla/>

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

--- 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:4c08f0dde4c2a48931a61b84a00d5c16f4b0e291

commit r14-7181-g4c08f0dde4c2a48931a61b84a00d5c16f4b0e291
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Jan 12 11:22:04 2024 +0100

    sra: Punt for too large _BitInt accesses [PR113330]

    This is the case I was talking about in
    https://gcc.gnu.org/pipermail/gcc-patches/2024-January/642423.html
    and Zdenek kindly found a testcase for it.
    We can only create BITINT_TYPE with precision at most 65535, not 65536,
    so need to punt if we'd want to create it.

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

            PR tree-optimization/113330
            * tree-sra.cc (create_access): Punt for BITINT_TYPE accesses with
            too large size.

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

  parent reply	other threads:[~2024-01-12 10:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11  9:16 [Bug tree-optimization/113330] New: " zsojka at seznam dot cz
2024-01-11 14:11 ` [Bug tree-optimization/113330] " jakub at gcc dot gnu.org
2024-01-11 14:22 ` jakub at gcc dot gnu.org
2024-01-12 10:22 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-12 10:28 ` jakub at gcc dot gnu.org
2024-01-20 17:09 ` 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-113330-4-aqEOiST3ac@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).