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/105150] [9/10/11/12 Regression] ICE with -Ofast: verify_gimple failed Date: Thu, 07 Apr 2022 07:13:35 +0000 [thread overview] Message-ID: <bug-105150-4-PvHqfwHMgR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105150-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105150 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:973a2ce71f8dab559fbbfc34b59e39e047df74a6 commit r12-8041-g973a2ce71f8dab559fbbfc34b59e39e047df74a6 Author: Jakub Jelinek <jakub@redhat.com> Date: Thu Apr 7 09:10:58 2022 +0200 tree.cc: Add tree_builtin_call_types_compatible_p [PR105150] And here is the follow-up patch that does the argument checking on GENERIC. It ensures TYPE_MAIN_VARIANT == TYPE_MAIN_VARIANT compatibility on the arguments, except for pointer arguments where both builtin's prototype and actual arguments have to be pointers and satisfy tree_nop_conversion_p, and for promoted char/short arguments where argument need to have integral signed type tree_nop_conversion_p compatible with integer_type_node. 2022-04-07 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/105150 * tree.cc (tree_builtin_call_types_compatible_p): New function. (get_call_combined_fn): Use it. * gcc.dg/pr105150.c: New test.
next prev parent reply other threads:[~2022-04-07 7:13 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-04 16:43 [Bug c/105150] New: " gscfq@t-online.de 2022-04-04 17:16 ` [Bug tree-optimization/105150] " jakub at gcc dot gnu.org 2022-04-04 17:58 ` jakub at gcc dot gnu.org 2022-04-05 6:52 ` rguenth at gcc dot gnu.org 2022-04-05 9:21 ` rguenth at gcc dot gnu.org 2022-04-05 9:30 ` [Bug c/105150] " pinskia at gcc dot gnu.org 2022-04-06 8:13 ` cvs-commit at gcc dot gnu.org 2022-04-06 14:49 ` cvs-commit at gcc dot gnu.org 2022-04-07 7:13 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-07 7:20 ` [Bug c/105150] [9/10/11 " jakub at gcc dot gnu.org 2022-04-07 7:21 ` rguenther at suse dot de 2022-05-27 9:47 ` [Bug c/105150] [10/11 " rguenth at gcc dot gnu.org 2022-06-28 10:48 ` jakub at gcc dot gnu.org 2023-07-07 10:42 ` [Bug c/105150] [11 " rguenth at gcc dot gnu.org 2024-03-10 4:39 ` pinskia 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-105150-4-PvHqfwHMgR@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).