Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 15 Apr 2016 22:38:33 +0200
From: Szabolcs Nagy <nsz@...t70.net>
To: musl@...ts.openwall.com
Subject: Re: [PATCH v2] add powerpc64 port

* Szabolcs Nagy <nsz@...t70.net> [2016-04-14 15:42:13 +0200]:
> * Bobby Bingham <koorogi@...rogi.info> [2016-04-14 03:01:38 -0500]:
> > 
> > How important is it to match glibc here?
> > 
> 
> i think we don't care about abi compat
> (but it might be interesting to check how much abi
> difference there is between glibc and musl, i can
> do this if i can build a musl+glibc toolchain)
> 

attached some c++ abi comparisions

(the comparision was not entirely clean, it involved
various manual hacks, but most types and functions
should be compared correctly glibc vs musl)

two interesting gcc warnings:

powerpc64 elf_vrreg_t (both musl and glibc):
note: the ABI of passing aggregates with 16-byte alignment has changed in GCC 5

x86_64 struct inotify_event (musl only):
note: the ABI of passing struct with a flexible array member has changed in GCC 4.4


View attachment "abi_type.powerpc64le.diff" of type "text/x-diff" (5984 bytes)

View attachment "abi_func.powerpc64le.diff" of type "text/x-diff" (5519 bytes)

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.