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 c/107993] ICE: tree check: expected string_cst, have integer_cst in get_target_clone_attr_len, at tree.cc:14872 Date: Mon, 09 Jan 2023 10:51:17 +0000 [thread overview] Message-ID: <bug-107993-4-GR4DEy4lPK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107993-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107993 --- Comment #6 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:befd29d5fe15c09638f73eeeb1f8a9e62ce569ee commit r13-5063-gbefd29d5fe15c09638f73eeeb1f8a9e62ce569ee Author: Martin Liska <mliska@suse.cz> Date: Tue Dec 27 16:31:57 2022 +0100 c: check if target_clone attrs are all string PR c/107993 gcc/c-family/ChangeLog: * c-attribs.cc (handle_target_clones_attribute): Check for string constant for all target_clone attribute values. gcc/testsuite/ChangeLog: * gcc.target/i386/pr107993.c: New test.
next prev parent reply other threads:[~2023-01-09 10:51 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-06 18:03 [Bug c/107993] New: " gscfq@t-online.de 2022-12-06 18:55 ` [Bug c/107993] " pinskia at gcc dot gnu.org 2022-12-09 9:48 ` marxin at gcc dot gnu.org 2022-12-23 15:44 ` marxin at gcc dot gnu.org 2022-12-27 15:07 ` marxin at gcc dot gnu.org 2022-12-28 8:18 ` marxin at gcc dot gnu.org 2022-12-28 9:01 ` marxin at gcc dot gnu.org 2023-01-09 10:51 ` cvs-commit at gcc dot gnu.org [this message] 2023-01-09 10:51 ` 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-107993-4-GR4DEy4lPK@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).