Skip to content
This repository has been archived by the owner on Aug 14, 2020. It is now read-only.

schema: add ppc64le/ppc64 as valid linux archs #639

Merged
merged 1 commit into from
Jul 15, 2016

Conversation

lucab
Copy link
Contributor

@lucab lucab commented Jul 13, 2016

This adds labeling for the two endian variants of ppc64:
ppc64le for little-endian and ppc64 for big-endian.

These explicitly correspond to uname -m on Linux systems.

@s-urbaniak
Copy link
Contributor

lgtm

@glevand
Copy link
Contributor

glevand commented Jul 13, 2016

Two wrongs don't make a right, so I would say use ppc64 and ppc64le.

@lucab
Copy link
Contributor Author

lucab commented Jul 13, 2016

For reference, this is how they are labeled in other places:

  • Debian: ppc64, ppc64el
  • GOARCH: ppc64, ppc64le
  • uname -m: ppc64, ppc64le

Bikeshedding level, may need a tie-breaker. @jonboulle?

@jonboulle
Copy link
Contributor

I think we should go with @glevand 's suggestion/uname -m in this case; we do want to be consistent with external sources where appropriate (and arguably ppc64/ppc64el is consistent with appc's aarch64/aarch64_be anyway - one "normal", one with endianness specifically called out). We went with the weird arm7 labels at the recommendation of ARM engineers.

@lucab lucab force-pushed the to-upstream/ppc64-labels branch from 7b4b40b to 4e6d9ef Compare July 14, 2016 16:47
This adds labeling for the two endian variants of ppc64:
`ppc64le` for little-endian and `ppc64` for big-endian.

These explicitly correspond to `uname -m` on Linux systems.
@lucab lucab force-pushed the to-upstream/ppc64-labels branch from 4e6d9ef to cf3fdbe Compare July 14, 2016 16:47
@lucab lucab changed the title schema: add ppc64l/ppc64b as valid linux archs schema: add ppc64le/ppc64 as valid linux archs Jul 14, 2016
@lucab
Copy link
Contributor Author

lucab commented Jul 14, 2016

Updated to use ppc64le and ppc64.

@jonboulle
Copy link
Contributor

LGTM

@jonboulle jonboulle merged commit 8ef926d into appc:master Jul 15, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants