mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Rich Felker <dalias@libc.org>,
	Gregor Richards <gregor.richards@uwaterloo.ca>,
	musl@lists.openwall.com
Subject: Re: musl libc for PPC64
Date: Mon, 8 Feb 2016 17:17:58 +0100	[thread overview]
Message-ID: <20160208161758.GG9915@port70.net> (raw)
In-Reply-To: <CAGWvnyk53uRfMe406GG=Ly07U-5Ze5vOkgjPd4JnL=oUbw9MBg@mail.gmail.com>

* David Edelsohn <dje.gcc@gmail.com> [2016-02-08 09:43:08 -0500]:
> What work is necessary to enable basic musl libc support for PPC64
> Linux Little Endian?

once the abi is clear (is long double ieee128?) the arch specific
parts of musl need to be ported for ARCH=powerpc64.

arch specific parts of musl are

arch/$ARCH
crt/$ARCH
src/*/$ARCH

porting check list:
http://www.openwall.com/lists/musl/2012/07/08/1

things that changed since:

- crt needs a small bit of inline asm in arch/$ARCH/crt_arch.h
  (which is used in crt/crt1.c and ldso/dlstart.c to align the
   stack, set up the argument and jump to the c entry point)

- arch/$ARCH/bits/foo.h is only needed if arch/generic/bits/foo.h
  is not good for the target. (getting the bits headers right
  is still a bit fiddly work: they have to match linux uapi.)

- fewer primitives are enough in arch/$ARCH/atomic_arch.h for
  an initial port (src/internal/atomic.h can implement most
  primitives in terms of a_cas or a_ll/a_sc).

- arch/$ARCH/pthread_arch.h has MC_PC instead of CANCEL_REG_IP
  (should be an mcontext member that can access the pc).

thinks that didnt change but not on that list:

- src/fenv/$ARCH/fenv.s is needed for fenv support

- configure script needs to be updated
  (compiler abi checks go here)

testing can be done against
http://repo.or.cz/libc-test.git

there are not many docs about the internals but the git log
is often informative.


  reply	other threads:[~2016-02-08 16:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 14:43 David Edelsohn
2016-02-08 16:17 ` Szabolcs Nagy [this message]
2016-02-08 16:51   ` Rich Felker
2016-02-08 17:48     ` David Edelsohn
2016-02-08 20:18       ` Rich Felker
2016-02-08 20:30         ` David Edelsohn
2016-02-08 22:59           ` Rich Felker
2016-02-08 23:24             ` David Edelsohn
2016-02-08 23:29               ` Rich Felker
2016-02-08 23:48                 ` Szabolcs Nagy
2016-02-09  1:03                   ` Szabolcs Nagy
2016-02-09  1:16                     ` David Edelsohn
2016-02-09  1:42                       ` Szabolcs Nagy
2016-02-09  1:45                       ` Szabolcs Nagy
2016-02-09  1:52                         ` Rich Felker
2016-02-09  2:06                           ` David Edelsohn
2016-02-10 22:17                           ` David Edelsohn
2016-02-08 23:52                 ` David Edelsohn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160208161758.GG9915@port70.net \
    --to=nsz@port70.net \
    --cc=dalias@libc.org \
    --cc=dje.gcc@gmail.com \
    --cc=gregor.richards@uwaterloo.ca \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).