public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bh@techhouse.brown.edu To: gcc-gnats@gcc.gnu.org Subject: other/5026: __attribute__ ((unused) seems misdocumented Date: Wed, 05 Dec 2001 20:46:00 -0000 [thread overview] Message-ID: <20011206044016.10363.qmail@sources.redhat.com> (raw) >Number: 5026 >Category: other >Synopsis: __attribute__ ((unused) seems misdocumented >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: doc-bug >Submitter-Id: net >Arrival-Date: Wed Dec 05 20:46:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Benoit Hudson >Release: 3.0.1 >Organization: >Environment: >Description: node (gcc.info)Function Attributes says: `unused' This attribute, attached to a function, means that the function is meant to be possibly unused. GCC will not produce a warning for this function. GNU C++ does not currently support this attribute as definitions without parameters are valid in C++. Does that last sentence make any sense at all? >How-To-Repeat: >Fix: Here's a possible rewriting which may be clearer overall: `unused' GCC -Wunused will warn about functions it finds that are not used. Attaching this attribute to a function will disable the warning for that function. >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2001-12-06 4:46 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=20011206044016.10363.qmail@sources.redhat.com \ --to=bh@techhouse.brown.edu \ --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).