mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Justin Cormack <justin@specialbusservice.com>
To: musl@lists.openwall.com
Subject: ppc64 ABI
Date: Sun, 19 Apr 2015 12:44:15 +0100	[thread overview]
Message-ID: <CAK4o1WyfuRoSCdp8LccK4b_LoRKUCKkd6b-MSY0mU=joL+QUAA@mail.gmail.com> (raw)

I am looking at doing a ppc64 port, and after some discussion on irc
last night wondering which ABI to port to.

ppc64 has two ABIs:
v1: as documented here
http://refspecs.linuxfoundation.org/ELF/ppc64/PPC-elf64abi-1.9.html
Slightly odd, as has function descriptors, so you cant just reference
a function pointer, mainly makes asm code messier as needs a header
for every function.
Traditionally bigendian. Fedora and Gentoo do distros, not sure there
are any others; FreeBSD support also exists.

v2, usually known as powerpc64le, helpfully. It is not little endian
exclusively, but there are no existing distros that are big endian.
Aim was to make it much closer to a standard ABI, so function pointers
are gone. IBM has been pushing this, and there are RedHat and Ubuntu
releases, targeting POWER8. (Which also means Ubuntu ships with cross
compilers for it).

I was thinking of doing a v1 port first then v2, partly as I have
little endian only hardware (Apple G5 running Fedora; Fedora has
recently dropped support though; ten years old but dual G5 is still
decent hardware). However maybe I should just skip to v2; I do have
access to hardware. In principal could then produce a bigendian Musl
distro for G5... IBM have been spending a fair amount of time making
sure software works with v2.

Both have 16 byte long double oddness.

Thoughts?


             reply	other threads:[~2015-04-19 11:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-19 11:44 Justin Cormack [this message]
2015-04-19 13:54 ` Szabolcs Nagy
2015-04-19 14:40   ` Justin Cormack
2015-04-19 15:13     ` Rich Felker
2015-04-19 15:12 ` Rich Felker
2015-04-19 17:01   ` Justin Cormack

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='CAK4o1WyfuRoSCdp8LccK4b_LoRKUCKkd6b-MSY0mU=joL+QUAA@mail.gmail.com' \
    --to=justin@specialbusservice.com \
    --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).