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/100791] ICE: verify_gimple failed Date: Fri, 28 May 2021 12:25:56 +0000 [thread overview] Message-ID: <bug-100791-4-5Oknd13y1Q@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100791-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100791 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:359c0a86e2974a9f3036bc05b6e6c661f2c463cf commit r12-1113-g359c0a86e2974a9f3036bc05b6e6c661f2c463cf Author: Richard Biener <rguenther@suse.de> Date: Fri May 28 13:31:35 2021 +0200 ipa/100791 - copy fntype when processing __builtin_va_arg_pack This missing copying exposed a type mismatch in the IL. 2021-05-28 Richard Biener <rguenther@suse.de> PR ipa/100791 * tree-inline.c (copy_bb): When processing __builtin_va_arg_pack copy fntype from original call. * gcc.dg/pr100791.c: New testcase.
next prev parent reply other threads:[~2021-05-28 12:25 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-27 5:23 [Bug c/100791] New: " cnsun at uwaterloo dot ca 2021-05-27 14:19 ` [Bug c/100791] " marxin at gcc dot gnu.org 2021-05-28 10:37 ` [Bug ipa/100791] " rguenth at gcc dot gnu.org 2021-05-28 11:26 ` rguenth at gcc dot gnu.org 2021-05-28 12:25 ` cvs-commit at gcc dot gnu.org [this message] 2021-05-28 12:29 ` [Bug ipa/100791] [10/11 Regression] " rguenth at gcc dot gnu.org 2021-06-16 13:12 ` cvs-commit at gcc dot gnu.org 2021-06-16 14:24 ` [Bug ipa/100791] [10 " cvs-commit at gcc dot gnu.org 2021-06-16 14:25 ` 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-100791-4-5Oknd13y1Q@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: linkBe 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).