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 ipa/109303] [13 Regression] ICE in push_agg_values_from_plats, at ipa-cp.cc:1458 since r13-3358-ge0403e95689af7d5
Date: Wed, 29 Mar 2023 16:26:53 +0000	[thread overview]
Message-ID: <bug-109303-4-82zRoFmjwW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109303-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
And the problem is similar to PR108605, most of IPA uses unsigned int as type
for byte offsets and while some spots check for offsets while bit offsets are
typically using HOST_WIDE_INT.  So, some larger bit offsets can't be
represented in unsigned int byte offset.

  parent reply	other threads:[~2023-03-29 16:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27 18:41 [Bug c/109303] New: [13 Regression] ICE in push_agg_values_from_plats, at ipa-cp.cc:1458 gscfq@t-online.de
2023-03-27 18:52 ` [Bug ipa/109303] " pinskia at gcc dot gnu.org
2023-03-27 20:06 ` [Bug ipa/109303] [13 Regression] ICE in push_agg_values_from_plats, at ipa-cp.cc:1458 since r13-3358-ge0403e95689af7d5 marxin at gcc dot gnu.org
2023-03-28  7:22 ` rguenth at gcc dot gnu.org
2023-03-29 15:37 ` jakub at gcc dot gnu.org
2023-03-29 16:26 ` jakub at gcc dot gnu.org [this message]
2023-03-29 16:40 ` jakub at gcc dot gnu.org
2023-03-29 22:20 ` jamborm at gcc dot gnu.org
2023-03-30  7:21 ` jakub at gcc dot gnu.org
2023-03-30  7:28 ` jakub at gcc dot gnu.org
2023-03-30 16:48 ` jamborm at gcc dot gnu.org
2023-03-31  8:51 ` jamborm at gcc dot gnu.org
2023-04-03 14:01 ` cvs-commit at gcc dot gnu.org
2023-04-03 14:02 ` jamborm at gcc dot gnu.org
2023-04-05  8:40 ` marxin at gcc dot gnu.org
2023-04-05  8:40 ` marxin 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-109303-4-82zRoFmjwW@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).