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
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
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 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
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
w
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 h
Mark Mitchell wrote:
> I'm sorry this is dragging out, but I think it's worth getting this bug
> fixed.
No need for apologies; you're doing the "right thing".
..Scott
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