lkml.org 
[lkml]   [2003]   [Feb]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: gcc 2.95 vs 3.21 performance
    Date
    >  > Maybe we should create a KGCC fork, optimise it for kernel
    > > complilations, then try to get our changes merged back in to GCC
    > > mainline at a later date.
    >
    > What exactly do you mean by "optimise for kernel compilations" ?

    I don't, that was a bad way of phrasing it - I didn't mean fork GCC
    just to create one which compiles the kernel so it runs faster, as the
    expense of other code.

    What I was thinking was that if we forked GCC, we could try out all of
    these ideas that have been floating around in this thread, and if, as
    was hinted at earlier in this thread, $bigcompanies[] have not offered
    contributions because of reluctance to accept them by the GCC team, we
    would be more in a position to try them out, because we only need to
    concern ourselves with breaking the compilation of the kernel, not
    every single program that currently compiles with GCC.

    The way I see it, the development series would be optimised for KGCC,
    and when we start to think about stabilising that development series,
    we try to get our KGCC changes merged back in to GCC mainline. If
    they are not accepted, either KGCC becomes the recommended kernel
    compiler, which should cause no great difficulties, (having one
    compiler for kernels, and one for userland applications), or we start
    making sure that we haven't broken compilation with GCC, (and since a
    there would probably always be people compiling with GCC anyway, even
    if there was a KGCC, we would effectively always know if we broke
    compilation with GCC), and then the recommended compiler is just not
    the optimal one, and it would be up to the various distributions to
    decide which one they are going to use.

    John.
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:32    [W:2.949 / U:0.036 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site