This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: RFA: GCC 4.2.1: Stabalizing coalesce_list's qsort


On 31 August 2007 14:29, Andrew MacLeod wrote:

> On Fri, 2007-08-31 at 14:28 +0200, Richard Guenther wrote:
>> On 8/31/07, Nick Clifton <nickc@redhat.com> wrote:
>>> Hi Richard,
>>> 
>>>> No, but for trunk if you bootstrapped/tested this.  That is, this patch
>>>> is ok for mainline if you did.
>>> 
>>> I have not (yet) applied this patch to the mainline.  The patched sources
>>> do bootstrap without problems, but I could not find any way to reproduce
>>> the original bug.  (ie the problem with a cygwin based mips compiler
>>> producing non-working code whereas a linux based mips compiler produced
>>> working code).  I even tried deliberately destabilizing the sort, but the
>>> current mainline sources do not appear to have any requirements of
>>> stability. 
>>> 
>>> Since stabilizing the sort would slow it down, I thought it best to check
>>> to make sure that it is still OK to apply the patch.  ie are we
>>> preferring host independence over compile speed ?
>> 
>> Yes.  I don't think the slowdown will be noticable.
> 
> And if it is, I will fix it by doing something different.
> 

  And nobody said otherwise when I asked if host independence wasn't as
important as -g independence, so I think we do prefer it at any cost.  (Well,
not at /any/ cost, but YKWIM).

(Will submit a patch to the coding/portability conventions at the weekend when
I have some spare minutes).


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]