public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: timb@bluearc.com To: gcc-gnats@gcc.gnu.org Subject: c++/7614: Warning when function returning reference to volatile called in void context Date: Fri, 16 Aug 2002 11:26:00 -0000 [thread overview] Message-ID: <20020816171523.26612.qmail@sources.redhat.com> (raw) >Number: 7614 >Category: c++ >Synopsis: Warning when function returning reference to volatile called in void context >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Aug 16 10:16:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: timb@bluearc.com >Release: 3.2 >Organization: >Environment: Debian GNU/Linux x86 unstable >Description: Was rather surprised to be deluged with warnings of the form "object of type `volatile X&' will not be accessed in statement" for practically every use of a volatile assignment operator. After much head-scratching, I found that it seems to be generated whenever a function returning a reference to volatile is called in a void context. It doesn't seem to be possible to disable this warning. >From the long comment above convert_to_void() in gcc/cp/cvt.c, it appears that this behaviour is intentional. However, if the intention is indeed to reduce confusion, then IMHO it actually has the reverse effect. It also seems inconsistent to generate the warning for a reference but not a pointer. >How-To-Repeat: Here's a simple snippet that demonstrates the problem:- volatile int& wibble(volatile int& x) { x = 0; return x; } volatile int v; void foo() { wibble(v); } >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-08-16 17:16 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-16 11:26 timb [this message] 2002-09-13 15:54 nathan
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=20020816171523.26612.qmail@sources.redhat.com \ --to=timb@bluearc.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).