public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: jbuck@synopsys.com To: gcc-gnats@gcc.gnu.org Subject: c++/9165: [3.3/3.4 regression] false "defined but not used" warnings Date: Sat, 04 Jan 2003 00:16:00 -0000 [thread overview] Message-ID: <20030104001211.1244.qmail@sources.redhat.com> (raw) >Number: 9165 >Category: c++ >Synopsis: [3.3/3.4 regression] false "defined but not used" warnings >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Jan 03 16:16:01 PST 2003 >Closed-Date: >Last-Modified: >Originator: Joe Buck >Release: 3.3-pre, 3.4-experimental >Organization: >Environment: GNU/Linux i686 (though probably all) >Description: gcc 3.3-pre and 3.4-experimental issue "defined but not used" warnings for static class objects whose destructors do cleanup operations. This is a more dangerous regression than it may appear, because it may inspire programmers to remove needed code from their applications, resulting in leaks and other failures. This is especially likely in shops that ask for clean -Wall compiles. This problem is not in gcc 3.2.1 or earlier versions. >How-To-Repeat: Compile with "gcc -c -O -Wall cleanup.cxx" where cleanup.cxx is ------------------------------ void do_cleanups(); class Cleanup { public: ~Cleanup() { do_cleanups();} }; static Cleanup dummy; --------------------------------- and get cleanup.cpp:8: warning: `Cleanup dummy' defined but not used >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-01-04 0:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-04 0:16 jbuck [this message] 2003-01-06 22:46 Janis Johnson 2003-01-06 23:07 bangerth 2003-01-07 2:44 mmitchel
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=20030104001211.1244.qmail@sources.redhat.com \ --to=jbuck@synopsys.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).