[lkml]   [2003]   [Jun]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Crusoe's persistent translation on linux?
    > The translations are usually _better_ than statically compiled native 
    > code (because the whole CPU is designed for speculation, and the static
    > compilers don't know how to do that), and thus going to native mode is not
    > necessarily a performance improvement.

    Would it be possible, (with relevant documentation), to tune the code
    morphing software for optimum performance of code generated by a
    specific compiler, though?

    If a particular version of GCC favours certain constructs and uses
    particular sets of registers for a given piece of code, couldn't we
    optimise for those cases, at the expense of others? Maybe a
    particular compiler doesn't use certain X86 instructions at all, and
    these could be eliminated altogether?

    It's not unlikely that an entirely open source system could have all
    code compiled with the same compiler, and so maybe we can use this to
    avoid implementing expensive corner cases in the CPU, because we're
    never going to trigger them.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:36    [W:0.021 / U:59.700 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site