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/102762] [10 Regression] ICE with -O2: Segmentation fault, memcpy, copy_bb
Date: Thu, 17 Feb 2022 10:48:14 +0000 [thread overview]
Message-ID: <bug-102762-4-IVwLCkpnKI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102762-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102762
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:724177df8e159dc3f70cd0e13a598e10dd321f37
commit r10-10462-g724177df8e159dc3f70cd0e13a598e10dd321f37
Author: Richard Biener <rguenther@suse.de>
Date: Fri Oct 15 08:41:57 2021 +0200
ipa/102762 - fix ICE with invalid __builtin_va_arg_pack () use
We have to be careful to not break the argument space calculation.
If there's not enough arguments just do not append any.
2021-10-15 Richard Biener <rguenther@suse.de>
PR ipa/102762
* tree-inline.c (copy_bb): Avoid underflowing nargs.
* gcc.dg/torture/pr102762.c: New testcase.
(cherry picked from commit 11a4714860d2df6ba496d55379e7dc702d5fc425)
next prev parent reply other threads:[~2022-02-17 10:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 3:00 [Bug c/102762] New: " cnsun at uwaterloo dot ca
2021-10-15 3:27 ` [Bug ipa/102762] [10/11/12 Regression] " pinskia at gcc dot gnu.org
2021-10-15 6:37 ` rguenth at gcc dot gnu.org
2021-10-15 7:34 ` cvs-commit at gcc dot gnu.org
2021-10-15 7:34 ` [Bug ipa/102762] [10/11 " rguenth at gcc dot gnu.org
2021-11-08 12:35 ` cvs-commit at gcc dot gnu.org
2022-02-17 10:48 ` cvs-commit at gcc dot gnu.org [this message]
2022-02-17 10:50 ` [Bug ipa/102762] [10 " rguenth 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-102762-4-IVwLCkpnKI@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).