H. J. Lu writes:
> On Wed, Mar 01, 2006 at 03:19:18PM +, Andrew Haley wrote:
> > H. J. Lu writes:
> > > On Wed, Mar 01, 2006 at 02:11:21PM +, Andrew Haley wrote:
> > > > H. J. Lu writes:
> > > > >
> > > > > The fix was posted at
> > > > >
> > > > > http://gcc.gnu.org/ml/
On Wed, Mar 01, 2006 at 03:19:18PM +, Andrew Haley wrote:
> H. J. Lu writes:
> > On Wed, Mar 01, 2006 at 02:11:21PM +, Andrew Haley wrote:
> > > H. J. Lu writes:
> > > >
> > > > The fix was posted at
> > > >
> > > > http://gcc.gnu.org/ml/gcc-patches/2004-09/msg01486.html
> > >
H. J. Lu writes:
> On Wed, Mar 01, 2006 at 02:11:21PM +, Andrew Haley wrote:
> > H. J. Lu writes:
> > >
> > > The fix was posted at
> > >
> > > http://gcc.gnu.org/ml/gcc-patches/2004-09/msg01486.html
> >
> > If it still works, please check it in.
>
> Ooops. The correct patch i
On Wed, Mar 01, 2006 at 02:11:21PM +, Andrew Haley wrote:
> H. J. Lu writes:
> > On Wed, Mar 01, 2006 at 11:48:39AM +, Andrew Haley wrote:
> > > Andrew Haley writes:
> > > > Andrew Pinski writes:
> > > > > With clean sources on x86_64-linux-gnu, I am getting almost all
> tests
> >
H. J. Lu writes:
> On Wed, Mar 01, 2006 at 11:48:39AM +, Andrew Haley wrote:
> > Andrew Haley writes:
> > > Andrew Pinski writes:
> > > > With clean sources on x86_64-linux-gnu, I am getting almost all
> > tests
> > > > for running gij to fail. Does anyone know what is going on he