lkml.org 
[lkml]   [2011]   [Mar]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    SubjectRe: X32 psABI status update
    From
    On Tue, Mar 15, 2011 at 10:24 PM, Mike Frysinger <vapier@gentoo.org> wrote:
    > On Wednesday, March 16, 2011 00:51:37 H.J. Lu wrote:
    >> On Tue, Mar 15, 2011 at 9:30 PM, Mike Frysinger <vapier@gentoo.org> wrote:
    >> > On Wednesday, March 16, 2011 00:17:04 H.J. Lu wrote:
    >> >> On Mon, Mar 7, 2011 at 1:33 PM, Mike Frysinger wrote:
    >> >> > On Saturday, March 05, 2011 14:08:04 H.J. Lu wrote:
    >> >> >> Many x32 bugs are fixed in kernel, glibc, binutils and GCC:
    >> >> >>
    >> >> >> https://sites.google.com/site/x32abi/
    >> >> >>
    >> >> >> The major remaining issues are glibc/gcc testsuite failures,
    >> >> >> kernel core dump and signal handler unwind.
    >> >> >
    >> >> > are you getting a unique host tuple for this ?  or are you extending
    >> >> > x86_64- linux-gnu ?  so the only way of knowing which ABI is to check
    >> >> > for the output of the compiler+compiler flags ?
    >> >>
    >> >> x32 requires x32 enabled x86-64 kernel.
    >> >
    >> > ok, but that doesnt answer my question.  what are you passing to --target
    >> > ?
    >>
    >> See:
    >>
    >> https://sites.google.com/site/x32abi/
    >>
    >> You configure it as
    >>
    >> CC="gcc -mx32" ...../configure x86_64- linux-gnu
    >
    > that isnt what the page says.  it does say for glibc to do:
    >        CC="x32-gcc -mx32 " CXX="x32-g++ -mx32 " CFLAGS="-O2 -g"  ../configure
    >
    > but it doesnt say what to do for binutils or gcc itself.  obviously you cant
    > use the -mx32 flag when building the cross gcc for the first time since the
    > current native gcc wont support it.
    >
    > the invocation given for glibc implies that the proposed tuple is x32-linux-
    > gnu, but the GNU config project doesnt support that tuple and i didnt see
    > mention of it in the binutils or gcc sources.
    >
    > so we get back to my original e-mail:
    >        are you getting a unique host tuple for this ?  or are you extending
    >        x86_64-linux-gnu ?  so the only way of knowing which ABI is to check for
    >        the output of the compiler+compiler flags ?

    As I said, the target is x86_64- linux-gnu and you just add -mx32 to CFLAGS.
    The x86_64- linux-gnu binutils and GCC support x32.


    --
    H.J.
    --
    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: 2011-03-16 13:43    [W:0.035 / U:32.092 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site