From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1626 invoked by alias); 8 Mar 2012 21:14:57 -0000 Received: (qmail 1617 invoked by uid 22791); 8 Mar 2012 21:14:56 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 08 Mar 2012 21:14:41 +0000 From: "mib.bugzilla at gmail dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mib.bugzilla at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2012-03/txt/msg00699.txt.bz2 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); ^