public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: notbob@tessellation.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/10647: is_volatile<T> gets compilation warnings and reports references and functions as volatile
Date: Tue, 06 May 2003 22:56:00 -0000	[thread overview]
Message-ID: <20030506224648.17137.qmail@sources.redhat.com> (raw)


>Number:         10647
>Category:       c++
>Synopsis:       is_volatile<T> gets compilation warnings and reports references and functions as volatile
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue May 06 22:56:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Robert Allan Schwartz
>Release:        gcc version 3.2 20020927 (prerelease)
>Organization:
>Environment:
in bash via cygwin on windows 98 se
>Description:
I apologize in advance if I'm not reporting this "bug"
absolutely correctly. I haven't done this before. I
appreciate your patience. Thank you.

I believe my template should NOT get warnings, and should report references and functions as NOT volatile.

Is this "pilot error" or a compiler bug?
>How-To-Repeat:
g++ is_volatile.cpp
./a.exe
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="is_volatile.cpp"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="is_volatile.cpp"

dGVtcGxhdGUgPHR5cGVuYW1lIFQ+DQpjbGFzcyBpc192b2xhdGlsZSB7IHB1YmxpYzogc3RhdGlj
IGNvbnN0IGJvb2wgdmFsdWUgPSBmYWxzZTsgfTsNCg0KdGVtcGxhdGUgPHR5cGVuYW1lIFQ+DQpj
bGFzcyBpc192b2xhdGlsZTx2b2xhdGlsZSBUPiB7IHB1YmxpYzogc3RhdGljIGNvbnN0IGJvb2wg
dmFsdWUgPSB0cnVlOyB9Ow0KDQojaW5jbHVkZSA8aW9zdHJlYW0+DQoNCmludCBtYWluKCkNCnsN
CglzdGQ6OmNvdXQgPDwgImlzX3ZvbGF0aWxlPGJvb2wgJj46OnZhbHVlID0gIiA8PCBpc192b2xh
dGlsZTxib29sICY+Ojp2YWx1ZSA8PCBzdGQ6OmVuZGw7DQoNCglzdGQ6OmNvdXQgPDwgImlzX3Zv
bGF0aWxlPHZvaWQgKHZvaWQpPjo6dmFsdWUgPSAiIDw8IGlzX3ZvbGF0aWxlPHZvaWQgKHZvaWQp
Pjo6dmFsdWUgPDwgc3RkOjplbmRsOw0KCXN0ZDo6Y291dCA8PCAiaXNfdm9sYXRpbGU8aW50ICAo
dm9pZCk+Ojp2YWx1ZSA9ICIgPDwgaXNfdm9sYXRpbGU8aW50ICAodm9pZCk+Ojp2YWx1ZSA8PCBz
dGQ6OmVuZGw7DQoJc3RkOjpjb3V0IDw8ICJpc192b2xhdGlsZTxpbnQgIChpbnQgKT46OnZhbHVl
ID0gIiA8PCBpc192b2xhdGlsZTxpbnQgIChpbnQgKT46OnZhbHVlIDw8IHN0ZDo6ZW5kbDsNCg0K
CXJldHVybiAwOw0KfQ0K


             reply	other threads:[~2003-05-06 22:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06 22:56 notbob [this message]
2003-05-07  0:24 giovannibajo

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=20030506224648.17137.qmail@sources.redhat.com \
    --to=notbob@tessellation.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: link
Be 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).