public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@redhat.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: GCC 4.0.1 Status (2005-06-27)
Date: Tue, 28 Jun 2005 20:08:00 -0000	[thread overview]
Message-ID: <1119989226.4621.106.camel@localhost.localdomain> (raw)
In-Reply-To: <42C171DD.4090408@codesourcery.com>

On Tue, 2005-06-28 at 08:50 -0700, Mark Mitchell wrote:
> Jeffrey A Law wrote:
> > On Tue, 2005-06-28 at 00:20 -0700, Mark Mitchell wrote:
> > 
> >>As stated earlier, the only patches I'm considering for 4.0.1 at present 
> >>are wrong-code cases on primary platforms.  There are several open, but 
> >>the only one I consider a show-stopper is PR 22051, which Jeff Law is 
> >>working on, and hopes to fix Tuesday.  As soon as that's in, I'll build 
> >>RC3, and then, hopefully, a few days later, put out the final release.
> >>
> >>I'm sorry this is dragging out, but I think it's worth getting this bug 
> >>fixed.
> > 
> > I'm working on it right now.    My PA box is experiencing cpu faults
> > on its second cpu while trying to bootstrap for a set of baseline
> > results....   I suspect it'll take until late tomorrow before I can get
> > a set of baseline test results, fix the bug, then get a set of new test
> > results for comparison purposes.
> 
> 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.
Eric C was kind enough to point me to a couple HPUX boxes elsewhere
in Red Hat.  I'm prepping a baserun right now and I've got a patch
that I'll test immediately afterwards.

jeff


      parent reply	other threads:[~2005-06-28 20:08 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
2005-06-28 18:38     ` Jeffrey A Law
2005-06-28 20:08     ` Jeffrey A Law [this message]

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=1119989226.4621.106.camel@localhost.localdomain \
    --to=law@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --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).