public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Marco.Franzen@bigfoot.com To: gcc-gnats@gcc.gnu.org Subject: c/6939: taking sizeof array parameter should trigger a warning Date: Wed, 05 Jun 2002 14:16:00 -0000 [thread overview] Message-ID: <20020605210610.15872.qmail@sources.redhat.com> (raw) >Number: 6939 >Category: c >Synopsis: taking sizeof array parameter should trigger a warning >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: change-request >Submitter-Id: net >Arrival-Date: Wed Jun 05 14:16:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Marco Franzen >Release: gcc-3.1 >Organization: >Environment: >Description: Neither the C nor the C++ front-end of GCC 3.1 issues a warning for this. (I tried -W -Wall for both.) I know the generated code is absolutely correct, but a warning would be in order (and should probably be on by default, given it will be rare outside obfuscation contests). >How-To-Repeat: int func(int array[], int* pointer) { int n1 = sizeof(array); // no, it isn't int n2 = sizeof(pointer); return n1 - n2; } int main() { int v[] = {1, 2, 3, 4, 5, 6, 7, 8, 9, 10}; return func (v, v); } >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2002-06-05 21:16 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020605210610.15872.qmail@sources.redhat.com \ --to=marco.franzen@bigfoot.com \ --cc=gcc-gnats@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).