From: Jason R Thorpe <thorpej@wasabisystems.com>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: gcc-patches@gcc.gnu.org, jakub@redhat.com, rth@redhat.com
Subject: Re: [PATCH] Fix some -Wunreachable-code issues
Date: Tue, 05 Nov 2002 14:08:00 -0000 [thread overview]
Message-ID: <20021105140852.G27156@dhcp7.wlan.shagadelic.org> (raw)
In-Reply-To: <200211030110.gA31AJpQ016617@hiauly1.hia.nrc.ca>; from dave@hiauly1.hia.nrc.ca on Sat, Nov 02, 2002 at 08:10:19PM -0500
On Sat, Nov 02, 2002 at 08:10:19PM -0500, John David Anglin wrote:
> I can't duplicate the PR on hppa2.0w-hp-hpux11.11 or hppa64-hp-hpux11.11.
> Jakub's patch might have fixed this PR.
Ah, I think I know why that PR doesn't trip anymore -- there is no
comparison in the for() statement. I had filed another PR containing
a Duff's Device, which Richard closed as a duplicate. The test case
in my PR still causes a bogus warning.
I'm writing up a few testsuite tests using a Duff's Device, and will
post them shortly.
--
-- Jason R. Thorpe <thorpej@wasabisystems.com>
next prev parent reply other threads:[~2002-11-05 22:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-02 10:07 John David Anglin
2002-11-02 16:47 ` Jason R Thorpe
2002-11-02 17:10 ` John David Anglin
2002-11-03 15:30 ` Richard Henderson
2002-11-05 14:08 ` Jason R Thorpe [this message]
2002-11-05 15:15 ` Jason R Thorpe
2002-11-05 15:20 ` Richard Henderson
2002-11-05 18:42 ` Jason R Thorpe
2002-11-18 14:16 ` Richard Henderson
2002-11-05 15:22 ` John David Anglin
2002-11-05 19:25 ` Jason R Thorpe
-- strict thread matches above, loose matches on Subject: below --
2002-02-12 9:36 Jakub Jelinek
2002-02-12 11:07 ` Richard Henderson
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=20021105140852.G27156@dhcp7.wlan.shagadelic.org \
--to=thorpej@wasabisystems.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=rth@redhat.com \
/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).