public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: jhi@iki.fi To: gcc-gnats@gcc.gnu.org Subject: c/7860: few new suggested warnings Date: Sun, 08 Sep 2002 15:06:00 -0000 [thread overview] Message-ID: <20020908220508.7220.qmail@sources.redhat.com> (raw) >Number: 7860 >Category: c >Synopsis: few new suggested warnings >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: change-request >Submitter-Id: net >Arrival-Date: Sun Sep 08 15:06:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Jarkko hietaniemi >Release: any >Organization: >Environment: any >Description: I was the release manager of the Perl 5.8.0 project. As a part of that, we did a lot of test building on many platforms to clean up the C source code of Perl, and saw a lot of warnings about dubious practices that gcc didn't catch. Therefore, I would like to suggest adding these warnings to some upcoming gcc release. Some of the suggested warnings are already there but one needs either -ansi or -pedantic to enable them, and in some projects (including Perl) this is not an option, therefore having the warnings still available separately would be a good thing. (In general, maybe "disassembling" -ansi and -pedantic into separate options would be beneficial?) Some of the suggested warnings do not seem to be there and therefore they would be completely new. The suggested warnings are in the file attachment. >How-To-Repeat: >Fix: Implement the new warnings :-) >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/x-macbinary; name="gccneedwarn" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="gccneedwarn" AAtnY2NuZWVkd2FybgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQpAAAAALmhQPS5oUD0AAAAbUJJTgAAAAAAAAAA AAAAAAAAAACCgYstAAAtV2NwcGNvbW1lbnQKCiAgICAgICAgV2FybiBhYm91dCBDKysgc3R5bGUg Y29tbWVudHMgLy8gbGlrZSB0aGlzLgoKLVdnbnVleHRlbnNpb25zCgogICAgICAgIFdhcm4gYWJv dXQgdGhlIHVzZSBvZiBhbnkgR05VIGV4dGVuc2lvbnMuCgotV3BvaW50ZXItaW1wbGljaXQtc2ln bgoKICAgICAgICBXYXJuIGlmIGEgcG9pbnRlciBpcyBpbXBsaWNpdGx5IGNhc3QgYmV0d2VlbiBz aWduZWQKICAgICAgICBhbmQgdW5zaWduZWQsIGZvciBleGFtcGxlOgoKICAgICAgICAgICAgaW50 IGZvbyh1bnNpZ25lZCBjaGFyICpzKSB7CiAgICAgICAgICAgICAgICAuLi4KICAgICAgICAgICAg fQogICAgICAgICAgICAgICAgLi4uCiAgICAgICAgICAgICAgICBjaGFyICpzOwogICAgICAgICAg ICAgICAgLi4uCiAgICAgICAgICAgICAgICBmb28ocyk7CgogICAgICAgIChlbmFibGVkIGJ5IC1h bnNpKQoKLVdlbnVtLWltcGxpY2l0LWludAoKICAgICAgICBXYXJuIGlmIGVudW1zIGFyZSBpbXBs aWNpdGx5IHVzZWQgYXMgaW50ZWdlcnMsIGZvciBleGFtcGxlCgogICAgICAgIGVudW0gZSB7IEUx LCBFMiwgRTMgfTsKICAgICAgICAuLi4KICAgICAgICBlbnVtIGUgZTEgPSAwOyAgLyogV2Fybi4g Ki8gCiAgICAgICAgZW51bSBlIGUyID0gRTI7CiAgICAgICAgZW51bSBlIGUzLCBlNDsKICAgICAg ICBlMyA9IGUxICsgMTsgICAgLyogV2Fybi4gKi8KICAgICAgICBlMisrOyAgICAgICAgICAgLyog V2Fybi4gKi8KICAgICAgICBlNCA9IGUzICYgfkUyOyAgLyogV2Fybi4gKi8gCgotV2VudW0tdHJh aWxpbmctY29tbWEKCiAgICAgICAgV2FybiBpZiBlbnVtIGRlY2xhcmF0aW9uIGhhcyBhIHRyYWls aW5nIGNvbW1hLgoKICAgICAgICAoZW5hYmxlZCBieSAtcGVkYW50aWMpCgotV2NwcC1zcHVyaW91 cy10b2tlbnMKCiAgICAgICAgV2FybiBpZiB0aGVyZSBhcmUgYW55IHVubmVjZXNzYXJ5IHRva2Vu cyBhZnRlciBwcmVwcm9jZXNzb3IgY29tbWFuZHMsCiAgICAgICAgZm9yIGV4YW1wbGUKCiAgICAg ICAgICAgICNlbmRpZiBTVFVGRgoKICAgICAgICAoZW5hYmxlZCBieSAtcGVkYW50aWMpCgoAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
next reply other threads:[~2002-09-08 22:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-09-08 15:06 jhi [this message] 2002-09-08 16:06 Andrew Pinski 2002-09-08 16:06 Jarkko Hietaniemi 2002-09-15 8:26 Jarkko Hietaniemi 2002-09-15 13:35 jsm28 2002-09-16 7:16 Jarkko Hietaniemi
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=20020908220508.7220.qmail@sources.redhat.com \ --to=jhi@iki.fi \ --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).