public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/107993] New: ICE: tree check: expected string_cst, have integer_cst in get_target_clone_attr_len, at tree.cc:14872
Date: Tue, 06 Dec 2022 18:03:08 +0000	[thread overview]
Message-ID: <bug-107993-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107993

            Bug ID: 107993
           Summary: ICE: tree check: expected string_cst, have integer_cst
                    in get_target_clone_attr_len, at tree.cc:14872
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Started with r6 :
(gcc configured with --enable-checking=yes)


$ cat z1.c
typedef union {} u;
__attribute__((target_clones("arch=alderlake",!"default")))
int f (u *x) {}


$ gcc-13-20221204 -c z1.c
z1.c:3:1: internal compiler error: tree check: expected string_cst, have
integer_cst in get_target_clone_attr_len, at tree.cc:14872
    3 | int f (u *x) {}
      | ^~~
0x6b3c56 tree_check_failed(tree_node const*, char const*, int, char const*,
...)
        ../../gcc/tree.cc:8822
0x121b83e tree_check(tree_node*, char const*, int, char const*, tree_code)
        ../../gcc/tree.h:3528
0x121b83e get_target_clone_attr_len(tree_node*)
        ../../gcc/tree.cc:14872
0x8fbf87 handle_target_clones_attribute
        ../../gcc/c-family/c-attribs.cc:5594
0x7b4a87 decl_attributes(tree_node**, tree_node*, int, tree_node*)
        ../../gcc/attribs.cc:878
0x7db93d start_function(c_declspecs*, c_declarator*, tree_node*)
        ../../gcc/c/c-decl.cc:10089
0x852e8e c_parser_declaration_or_fndef
        ../../gcc/c/c-parser.cc:2751
0x85e30f c_parser_external_declaration
        ../../gcc/c/c-parser.cc:1925
0x85ec4d c_parser_translation_unit
        ../../gcc/c/c-parser.cc:1779
0x85ec4d c_parse_file()
        ../../gcc/c/c-parser.cc:24596
0x8d85e1 c_common_parse_file()
        ../../gcc/c-family/c-opts.cc:1248

             reply	other threads:[~2022-12-06 18:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06 18:03 gscfq@t-online.de [this message]
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
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@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).