public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aaron at aaronballman dot com" <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:37:25 +0000 [thread overview] Message-ID: <bug-107980-4-Fs5qnCYC06@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 #5 from Aaron Ballman <aaron at aaronballman dot com> --- (In reply to Andrew Pinski from comment #3) > I think we should warn but how to warn is going to have to special case the > macro I think. I was contemplating a perhaps terrible idea of adding some new builtins: ``` unsigned __builtin_va_opt_count(...); void __builtin_c23_va_start(va_list list, unsigned arg_count); ``` and then doing something along these lines in stdarg.h: ``` #if defined(__STDC_VERSION__) && __STDC_VERSION__ >= 202000L #define va_start(ap, ...) __builtin_c23_va_start(ap, __builtin_va_opt_count(__VA_OPT__)) #else ... #endif ``` but I've not put enough thought into it yet. WDYT about something along those lines? (In reply to Andrew Pinski from comment #4) > (In reply to Andrew Pinski from comment #3) > > I think we should warn but how to warn is going to have to special case the > > macro I think. > > But saying that I do think it is valid C2X code if you take the C2X standard > seperately from the older standards. I'm sad I noticed this after the NB comment period closed for the US NB because otherwise I'd leave a comment to make it a constraint violation to pass more than two arguments to the macro (or at least a recommended practice to diagnose). Because I agree with you that the letter of the standard makes this valid in C2x, but given that the extra arguments are not expanded or evaluated, there is no reason to accept more than two arguments in any C standard version.
next prev parent reply other threads:[~2022-12-06 13:37 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 [this message] 2022-12-06 13:44 ` pinskia at gcc dot gnu.org 2022-12-06 13:51 ` jakub at gcc dot gnu.org 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-Fs5qnCYC06@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).