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 ipa/109303] [13 Regression] ICE in push_agg_values_from_plats, at ipa-cp.cc:1458 since r13-3358-ge0403e95689af7d5
Date: Mon, 03 Apr 2023 14:01:58 +0000 [thread overview]
Message-ID: <bug-109303-4-cnAIUDVsGA@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 #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Jambor <jamborm@gcc.gnu.org>:
https://gcc.gnu.org/g:da3fd01757297c1d20cf3dcd76046488da737569
commit r13-6986-gda3fd01757297c1d20cf3dcd76046488da737569
Author: Martin Jambor <mjambor@suse.cz>
Date: Mon Apr 3 15:53:36 2023 +0200
ipa: Avoid constructing aggregate jump functions with huge offsets (PR
109303)
We are in the process of changing data structures holding information
about constants passed by reference and in aggregates to use unsigned
int offsets rather than HOST_WIDE_INT (which was selected simply
because that is what fell out of get_ref_base_and_extent at that time)
in order to conserve memory, especially at WPA time.
PR 109303 testcase discovers that we do not properly check that we
only create jump functions with offsets (plus sizes) that fit into the
smaller type. This patch adds the necessary check.
gcc/ChangeLog:
2023-03-30 Martin Jambor <mjambor@suse.cz>
PR ipa/109303
* ipa-prop.cc (determine_known_aggregate_parts): Check that the
offset + size will be representable in unsigned int.
gcc/testsuite/ChangeLog:
2023-03-30 Jakub Jelinek <jakub@redhat.com>
Martin Jambor <mjambor@suse.cz>
PR ipa/109303
* gcc.dg/pr109303.c: New test.
next prev parent reply other threads:[~2023-04-03 14:01 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
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 [this message]
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-cnAIUDVsGA@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).