This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Don't use slowcompare method unconditionally
- From: Andrew Pinski <pinskia at physics dot uc dot edu>
- To: pinskia at physics dot uc dot edu (Andrew Pinski)
- Cc: jakub at redhat dot com, pinskia at physics dot uc dot edu (Andrew Pinski), gcc-patches at gcc dot gnu dot org
- Date: Wed, 9 Nov 2005 11:10:54 -0500 (EST)
- Subject: Re: [PATCH] Don't use slowcompare method unconditionally
>
> >
> > On Wed, Nov 09, 2005 at 10:42:46AM -0500, Andrew Pinski wrote:
> > > > Tested with make gnucompare, make fastcompare and make slowcompare,
> > > > each time with objects from a bootstrap, then with one . dir object modified
> > > > by hand and then with one libgcc/ dir object modified.
> > > >
> > > > Ok for HEAD?
> > >
> > > Coreutils has already been fixed. So why is this patch needed?
> >
> > I don't think so. I'm using coreutils-5.93, release apparently 3 days ago,
> > and it refuses tail +NNN form by default.
> > Of course I can use
> > _POSIX2_VERSION=199506 tail +16c instead of just tail +16c and it will
> > work, but that doesn't sound to me like "coreutils has already been fixed".
>
>
> >From http://gcc.gnu.org/ml/gcc-patches/2005-06/msg00993.html
>
> FYI, this has been recently fixed in the coreutils CVS. It's been a
> while since the last release -- I hope it won't take too long till we have
> the next one.
>
>
> So maybe they broke it again. I still think we should not change anything for
> a broken coreutils.
Actually it looks like coreutils only fixed "tail -1" and not "tail +16c".
http://lists.gnu.org/archive/html/bug-coreutils/2005-09/msg00232.html
This is still wrong and is still a broken coreutils and still should reported to
them.
-- Pinski