public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mib.bugzilla at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/52534] New: gcc doesn't detect incorrect expression in call to va_start Date: Thu, 08 Mar 2012 21:14:00 -0000 [thread overview] Message-ID: <bug-52534-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52534 Bug #: 52534 Summary: gcc doesn't detect incorrect expression in call to va_start Classification: Unclassified Product: gcc Version: 4.5.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: mib.bugzilla@gmail.com The C standard is very clear that the second argument to va_start is a parameter identifier, not an expression. For example, int maxof(int, ...) ; void f(void); int maxof(int n_args, ...){ register int i; int max, a; va_list ap; va_start(ap, (unsigned int)n_args); max = va_arg(ap, int); for(i = 2; i <= n_args; i++) { if((a = va_arg(ap, int)) > max) max = a; } va_end(ap); return max; } Intel compiler finds the bug: vaarg.c(12): error: incorrect use of va_start va_start(ap, (unsigned int)n_args); ^
next reply other threads:[~2012-03-08 21:14 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-08 21:14 mib.bugzilla at gmail dot com [this message] 2012-03-12 14:10 ` [Bug c/52534] " rguenth at gcc dot gnu.org 2012-03-15 9:49 ` pinskia at gcc dot gnu.org 2012-03-15 10:04 ` jakub at gcc dot gnu.org 2024-04-09 6:41 ` pinskia at gcc dot gnu.org 2024-04-09 11:06 ` jakub 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-52534-4@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).