|
Message-ID: <20150311133916.GA19360@port70.net> Date: Wed, 11 Mar 2015 14:39:17 +0100 From: Szabolcs Nagy <nsz@...t70.net> To: musl@...ts.openwall.com Subject: Re: aarch64 port * Rich Felker <dalias@...c.org> [2015-03-09 23:03:42 -0400]: > On Tue, Mar 10, 2015 at 03:44:46AM +0100, Szabolcs Nagy wrote: > > vdso works now > > Great! Can you confirm whether enabling it on 32-bit ARM would be okay 32 arm support vdso is not yet merged into the kernel > > > Yes, I'd like to add a copy (or just move it) at the end contingent > > > upon TLS_ABOVE_TP. > > > > i just added a todo about this > > Would you like me to make this change prior to committing aarch64 so > you could use the assumption that dtv is accessible at a fixed small > offset? i made a patch that does the copy > > i can add dummy long double functions that map to the double version > > > > missing ones (not counting complex): > > Are the complex ones ld-format-specific anyway? I figured they would > just be written in terms of real ld functions. you were right so i added dummy versions for the few missing math functions > > i changed the pthread types to match x86_64 as that seems to me > > the most reasonable approach > > Yes that's the way I'm leaning -- 40-byte rather than 32-byte. Having > the pthread types in the shared part of alltypes.h.in would be very > nice. doing that would be a separate commit (currently there are 3 versions: 32bit, 64bit, x32) attached all the patches, when they are applied aarch64 passes the tests View attachment "0001-copy-the-dtv-pointer-to-the-end-of-the-pthread-struc.patch" of type "text/x-diff" (2802 bytes) View attachment "0002-math-add-ld128-exp2l-based-on-the-freebsd-implementa.patch" of type "text/x-diff" (11828 bytes) View attachment "0003-math-add-dummy-implementations-of-128-bit-long-doubl.patch" of type "text/x-diff" (8498 bytes) View attachment "0004-add-aarch64-port.patch" of type "text/x-diff" (70699 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.