From: Mike Stump <mikestump@comcast.net>
To: sje@cup.hp.com
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [patch, testsuite] Fix g++.dg/opt/devirt2.C scanning, PR 48727
Date: Sat, 11 Jun 2011 17:53:00 -0000 [thread overview]
Message-ID: <B38FFE84-8215-4662-A017-ED1FE20E521E@comcast.net> (raw)
In-Reply-To: <201106101628.p5AGSXG20686@lucas.cup.hp.com>
On Jun 10, 2011, at 9:28 AM, Steve Ellcey wrote:
> I will check in this testsuite fix as obvious if there are no objections.
Thanks for the comments. When doing a port, having a comment on other port's issues with a testcase, is useful, as you get to say, gosh, I'm in that class too, and just blindly follow the same path for the same reason.
next prev parent reply other threads:[~2011-06-11 17:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 17:09 Steve Ellcey
2011-06-11 17:53 ` Mike Stump [this message]
2011-06-15 17:15 ` Hans-Peter Nilsson
2011-06-16 20:49 ` Steve Ellcey
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=B38FFE84-8215-4662-A017-ED1FE20E521E@comcast.net \
--to=mikestump@comcast.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=sje@cup.hp.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).