public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/7860: few new suggested warnings Date: Sun, 08 Sep 2002 16:06:00 -0000 [thread overview] Message-ID: <20020908230601.1610.qmail@sources.redhat.com> (raw) The following reply was made to PR c/7860; it has been noted by GNATS. From: Andrew Pinski <pinskia@physics.uc.edu> To: jhi@iki.fi Cc: gcc-gnats@gcc.gnu.org Subject: Re: c/7860: few new suggested warnings Date: Sun, 8 Sep 2002 18:57:44 -0400 Here is a copy of the file since the file was in macbinary format that some people cannot decode: -Wcppcomment Warn about C++ style comments // like this. -Wgnuextensions Warn about the use of any GNU extensions. -Wpointer-implicit-sign Warn if a pointer is implicitly cast between signed and unsigned, for example: int foo(unsigned char *s) { ... } ... char *s; ... foo(s); (enabled by -ansi) -Wenum-implicit-int Warn if enums are implicitly used as integers, for example enum e { E1, E2, E3 }; ... enum e e1 = 0; /* Warn. */ enum e e2 = E2; enum e e3, e4; e3 = e1 + 1; /* Warn. */ e2++; /* Warn. */ e4 = e3 & ~E2; /* Warn. */ -Wenum-trailing-comma Warn if enum declaration has a trailing comma. (enabled by -pedantic) -Wcpp-spurious-tokens Warn if there are any unnecessary tokens after preprocessor commands, for example #endif STUFF (enabled by -pedantic)
next reply other threads:[~2002-09-08 23:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-09-08 16:06 Andrew Pinski [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-09-16 7:16 Jarkko Hietaniemi 2002-09-15 13:35 jsm28 2002-09-15 8:26 Jarkko Hietaniemi 2002-09-08 16:06 Jarkko Hietaniemi 2002-09-08 15:06 jhi
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=20020908230601.1610.qmail@sources.redhat.com \ --to=pinskia@physics.uc.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).