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/104533] [12 Regression] ICE in update_vtable_references, at ipa-visibility.cc:383 since r12-2900-gfa28520fadb9405f Date: Tue, 01 Mar 2022 09:10:51 +0000 [thread overview] Message-ID: <bug-104533-4-oyynAtkOZw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104533-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104533 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Liska <marxin@gcc.gnu.org>: https://gcc.gnu.org/g:6df0c8d417fb33ea130e2957755a60483e9fd692 commit r12-7427-g6df0c8d417fb33ea130e2957755a60483e9fd692 Author: Martin Liska <mliska@suse.cz> Date: Mon Feb 28 13:27:22 2022 +0100 ipa: Improve error handling for target_clone single value PR ipa/104533 gcc/c-family/ChangeLog: * c-attribs.cc (handle_target_clones_attribute): Use get_target_clone_attr_len and report warning soon. gcc/ChangeLog: * multiple_target.cc (get_attr_len): Move to tree.c. (expand_target_clones): Remove single value checking. * tree.cc (get_target_clone_attr_len): New fn. * tree.h (get_target_clone_attr_len): Likewise. gcc/testsuite/ChangeLog: * g++.target/i386/pr104533.C: New test.
next prev parent reply other threads:[~2022-03-01 9:10 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-14 19:55 [Bug c++/104533] New: [12 Regression] ICE in update_vtable_references, at ipa-visibility.cc:383 gscfq@t-online.de 2022-02-15 8:03 ` [Bug ipa/104533] " rguenth at gcc dot gnu.org 2022-02-16 10:06 ` pinskia at gcc dot gnu.org 2022-02-22 10:12 ` [Bug ipa/104533] [12 Regression] ICE in update_vtable_references, at ipa-visibility.cc:383 since r12-2900-gfa28520fadb9405f marxin at gcc dot gnu.org 2022-03-01 9:10 ` cvs-commit at gcc dot gnu.org [this message] 2022-03-01 9:11 ` 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-104533-4-oyynAtkOZw@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).