public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/5802
Date: Thu, 08 May 2003 23:16:00 -0000 [thread overview]
Message-ID: <20030508231600.10919.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/5802; it has been noted by GNATS.
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: c++/5802
Date: Thu, 8 May 2003 18:08:26 -0500 (CDT)
Still present on yesterday's mainline.
I'm pretty sure the bug has to do with gcc's knowledge that the &&
operator can be short-cut: if the first part yields false, then the second
part isn't evaluated any more, so dptr isn't initialized. However, in that
case we would end up in the other branch of the if, in which we don't use
dptr, so the warning is useless there.
W.
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ices.utexas.edu
www: http://www.ices.utexas.edu/~bangerth/
reply other threads:[~2003-05-08 23:16 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=20030508231600.10919.qmail@sources.redhat.com \
--to=bangerth@ices.utexas.edu \
--cc=gcc-prs@gcc.gnu.org \
--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).