public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sebor at roguewave dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/35711] New: bad text in -Wcast-qual warning (forgets volatile)
Date: Wed, 26 Mar 2008 20:14:00 -0000 [thread overview]
Message-ID: <bug-35711-1186@http.gcc.gnu.org/bugzilla/> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
The text of the warning below is incorrect and misleading -- the cast
actually casts away the volatile qualifier, not constness. The warning
is misleading when the type of the source is both const and volatile
qualified.
$ cat t.cpp && g++ -c -Wcast-qual t.cpp
int* foo (volatile int *p)
{
return (int*)p;
}
t.cpp: In function ‘int* foo(volatile int*)’:
t.cpp:3: warning: cast from type ‘volatile int*’ to type ‘int*’ casts away
constness
--
Summary: bad text in -Wcast-qual warning (forgets volatile)
Product: gcc
Version: 4.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: sebor at roguewave dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35711
next reply other threads:[~2008-03-26 20:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 20:14 sebor at roguewave dot com [this message]
2008-03-27 14:15 ` [Bug c++/35711] " manu at gcc dot gnu dot org
2008-08-29 1:58 ` manu at gcc dot gnu dot org
2008-08-29 3:10 ` pinskia at gcc dot gnu dot org
2008-08-29 3:32 ` manu at gcc dot gnu dot org
2008-08-29 3:35 ` pinskia at gcc dot gnu dot org
2008-08-29 3:38 ` manu at gcc dot gnu dot org
2009-01-07 2:41 ` ian at airs dot com
2009-01-07 9:39 ` schwab at suse dot de
2009-01-07 14:27 ` ian at airs dot com
2009-01-07 15:35 ` joseph at codesourcery dot com
2009-01-07 15:42 ` ian at airs dot com
2009-02-08 15:52 ` manu at gcc dot gnu dot org
2009-04-21 19:49 ` manu at gcc dot gnu dot org
2009-04-21 19:53 ` manu at gcc dot gnu dot org
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=bug-35711-1186@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).