public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/107980] va_start does not warn about an arbitrary number of arguments in C2x mode Date: Tue, 06 Dec 2022 13:51:07 +0000 [thread overview] Message-ID: <bug-107980-4-WJqkQHWUAz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107980-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107980 --- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Why do you need a builtin for counting number of arguments in __VA_OPT__? That can be done in the preprocessor. All one needs is 1, 2 or more arguments.
next prev parent reply other threads:[~2022-12-06 13:51 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-05 20:46 [Bug c/107980] New: va_start incorrectly accepts an arbitrary number of arguments in C2x aaron at aaronballman dot com 2022-12-05 20:57 ` [Bug c/107980] " pinskia at gcc dot gnu.org 2022-12-05 21:04 ` aaron at aaronballman dot com 2022-12-05 21:10 ` [Bug c/107980] va_start does not warn about an arbitrary number of arguments in C2x mode pinskia at gcc dot gnu.org 2022-12-05 21:17 ` pinskia at gcc dot gnu.org 2022-12-06 13:37 ` aaron at aaronballman dot com 2022-12-06 13:44 ` pinskia at gcc dot gnu.org 2022-12-06 13:51 ` jakub at gcc dot gnu.org [this message] 2022-12-06 14:04 ` aaron at aaronballman dot com 2022-12-06 15:42 ` aaron at aaronballman dot com 2022-12-06 15:46 ` jakub at gcc dot gnu.org 2022-12-06 16:13 ` aaron at aaronballman dot com 2022-12-07 0:55 ` joseph at codesourcery dot com 2022-12-07 14:57 ` jakub at gcc dot gnu.org 2022-12-07 15:00 ` aaron at aaronballman dot com 2022-12-07 15:38 ` pinskia at gcc dot gnu.org 2022-12-07 16:42 ` aaron at aaronballman dot com 2022-12-07 18:29 ` joseph at codesourcery dot com
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-107980-4-WJqkQHWUAz@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).