From: Joe Buck <Joe.Buck@synopsys.COM>
To: Jeffrey A Law <law@redhat.com>
Cc: Mark Mitchell <mark@codesourcery.com>,
gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: GCC 4.0.1 Status (2005-06-27)
Date: Tue, 28 Jun 2005 16:15:00 -0000 [thread overview]
Message-ID: <20050628161539.GA9524@synopsys.com> (raw)
In-Reply-To: <1119974795.4621.83.camel@localhost.localdomain>
On Tue, Jun 28, 2005 at 10:06:35AM -0600, Jeffrey A Law wrote:
> On Tue, 2005-06-28 at 08:50 -0700, Mark Mitchell wrote:
> > Perhaps you could get a patch put together, test it by staring
> > atassembly output, and then ask for a volunteer to test it? I expect
> > that Joseph could do a test run on PA-HPUX for you.
> It might be the best bet. I'm going to clean out the bloody box
> to hopefully improve its airflow and give it one more shot.
I can also test hppa-hpux.
next prev parent reply other threads:[~2005-06-28 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 7:22 Mark Mitchell
2005-06-28 12:50 ` Scott Robert Ladd
2005-06-28 15:41 ` Jeffrey A Law
2005-06-28 15:51 ` Mark Mitchell
2005-06-28 16:07 ` Jeffrey A Law
2005-06-28 16:15 ` Joe Buck [this message]
2005-06-28 18:38 ` Jeffrey A Law
2005-06-28 20:08 ` Jeffrey A Law
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=20050628161539.GA9524@synopsys.com \
--to=joe.buck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=law@redhat.com \
--cc=mark@codesourcery.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).