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/105149] [9/10/11/12 Regression] ICE in verify_ssa, at tree-ssa.cc:1211 Date: Fri, 08 Apr 2022 07:17:42 +0000 [thread overview] Message-ID: <bug-105149-4-XCm4CBCoJH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105149-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105149 --- Comment #9 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:6e2743687202c58a6553ae632ebbada3de38ad48 commit r12-8057-g6e2743687202c58a6553ae632ebbada3de38ad48 Author: Jakub Jelinek <jakub@redhat.com> Date: Fri Apr 8 09:16:30 2022 +0200 c: Error on va_arg with function type [PR105149] In the PR Joseph said that the C standard for va_arg talks about pointers to object type and as a function type is not object type, it is invalid. The following patch diagnoses it in the FE, instead of ICEing later on when optimizations are turned on (and with -O0 doing something weird at runtime). 2022-04-08 Jakub Jelinek <jakub@redhat.com> PR c/105149 * c-typeck.cc (c_build_va_arg): Reject function types. * gcc.dg/pr105149.c: New test.
next prev parent reply other threads:[~2022-04-08 7:17 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-04 16:42 [Bug c/105149] New: " gscfq@t-online.de 2022-04-04 17:11 ` [Bug tree-optimization/105149] " jakub at gcc dot gnu.org 2022-04-05 6:50 ` rguenth at gcc dot gnu.org 2022-04-05 7:34 ` [Bug c/105149] " rguenth at gcc dot gnu.org 2022-04-05 7:37 ` rguenth at gcc dot gnu.org 2022-04-05 7:40 ` rguenth at gcc dot gnu.org 2022-04-05 7:43 ` rguenth at gcc dot gnu.org 2022-04-05 18:42 ` joseph at codesourcery dot com 2022-04-07 10:41 ` jakub at gcc dot gnu.org 2022-04-08 7:17 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-08 8:11 ` [Bug c/105149] [9/10/11 " jakub at gcc dot gnu.org 2022-05-27 9:47 ` [Bug c/105149] [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/105149] [11 " rguenth 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-105149-4-XCm4CBCoJH@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).