This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

c++/10647: is_volatile<T> gets compilation warnings and reports references and functions as volatile

From: notbob at tessellation dot com
To: gcc-gnats at gcc dot gnu dot org
Date: 6 May 2003 22:46:48 -0000
Subject: c++/10647: is_volatile<T> gets compilation warnings and reports references and functions as volatile
Reply-to: notbob at tessellation dot com

>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

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]