public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: calvin.austin@sun.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
hui.huang@sun.com, nobody@gcc.gnu.org
Subject: Re: c++/4584: [2003-01-21] Using null pointers for fake addressof() generates warnings
Date: Thu, 08 May 2003 22:05:00 -0000 [thread overview]
Message-ID: <20030508220545.6318.qmail@sources.redhat.com> (raw)
Synopsis: [2003-01-21] Using null pointers for fake addressof() generates warnings
State-Changed-From-To: analyzed->closed
State-Changed-By: bangerth
State-Changed-When: Thu May 8 22:05:45 2003
State-Changed-Why:
3.3 and present mainline say this:
g/x> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c 2810-2.ii
<internal>:6: warning: invalid access to non-static data member `X::p' of NULL
object
<internal>:6: warning: (perhaps the `offsetof' macro was used incorrectly)
I think the warning is valid, but if you don't like it you're
of course free to shut it off.
W.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4584
reply other threads:[~2003-05-08 22:05 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=20030508220545.6318.qmail@sources.redhat.com \
--to=bangerth@dealii.org \
--cc=calvin.austin@sun.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=hui.huang@sun.com \
--cc=nobody@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).