public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/100535] ICE: tree check: expected function_type or method_type, have integer_type in gimplify_call_expr, at gimplify.c:3457 Date: Fri, 08 Mar 2024 04:06:31 +0000 [thread overview] Message-ID: <bug-100535-4-hkjMPPsa1r@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100535-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100535 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED Target Milestone|--- |13.0 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Fixed in GCC 13: ``` <source>: In function 'foo': <source>:6:1: error: invalid argument to gimple call 6 | } | ^ __builtin_abs () t1_1 = __builtin_abs (__builtin_abs ()); ```
prev parent reply other threads:[~2024-03-08 4:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-11 16:14 [Bug c/100535] New: " cnsun at uwaterloo dot ca 2021-12-12 6:30 ` [Bug c/100535] " pinskia at gcc dot gnu.org 2024-03-08 4:06 ` pinskia at gcc dot gnu.org [this message]
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-100535-4-hkjMPPsa1r@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).