[lkml]   [1998]   [Jun]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: ___ 2.0.34-pre11 (and pre16 too) /dev/mem broken???
    On Wed, 3 Jun 1998, Alex Buell wrote:

    > Andrea Arcangeli wrote:
    > > >Even I have recompiled svgalib with gcc-2.8.1, it not works. ;-(
    > >
    > > Argggggggg, 2.0.x kernel ___________MUST____________ BE COMPILED WITH
    > > AND ONLY GCC-2.7.2.x!!!!!!!!!!
    > development glibc v2.1 releases requires gcc-2.8.1. :o( I don't really
    > want to have to upgrade to gcc-2.8.1 in order to use glibc v2.1, when I
    > have a perfectly good v2.7.2.3 compiler! Whose *insert your favourite
    > expletive here* decision was this, and why?

    Hi Alex,

    I think I can give a good reason to upgrade for glibc.

    Snag c-torture-1.45 and then run it on a bunch of compilers.
    test datafile failures pass glibc-2.0.94 make check?

    gcc- 73 did 2.0.6. HORROR story :)
    gcc- 115 never never again
    gcc-2.8.1.compile.out 32 all but 1
    gcc-2.8.1.execute.out 8
    testgcc-2.8.1.compile.out 32 yep, works great too
    testgcc-2.8.1.execute.out 8
    egcs-1.0.3.release.compile.out 32 nope
    egcs-1.0.3.release.execute.out 8
    egcs-2.91.34.compile.out 24 nope
    egcs-2.91.34.execute.out 16
    pgcc-2.91.28.compile.out 24 nope, aborts
    pgcc-2.91.28.execute.out 8

    If you use -O2 (tested), you will get some passes where I don't.



    (I use -O6 -fomit-frame-pointer for shared libs, -O2 for statics)

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to

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