-
Notifications
You must be signed in to change notification settings - Fork 633
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reformat "Platform Variants", especially to add amd64, ppc64le, riscv64 #1172
Conversation
This changes the table to be a line per ISA instead of per variant; adds x86-64, POWER8+, and RISC-V; and notes the appropriate "Go analog" in each case (because these values mirror Go's choices, like our use of `GOOS` and `GOARCH`). Of particular note, `GOARM64` and `GORISCV64` are not fully implemented or released in Go yet, but they are accepted proposals with in-progress implementations or already merged to main: - `GOARM64`: https://golang.org/issue/60905 - `GORISCV64`: https://golang.org/issue/61476#issuecomment-1791156741 Signed-off-by: Tianon Gravi <admwiggin@gmail.com>
dd2fe12
to
2d95dde
Compare
| ARM 32-bit, v7 | `arm` | `v7` | | ||
| ARM 32-bit, v8 | `arm` | `v8` | | ||
| ARM 64-bit, v8 | `arm64` | `v8` | | ||
These values SHOULD match (or be similar to) their analog listed in [the Go Language document][go-environment2]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(or be similar to)
This part makes me nuts, but I felt like I had to somehow address that GOARM
does not use a v
prefix, GOARM64
will not (at least initially) support v8
(without a minor, like v8.0
), we don't do extra things like softfloat
or sse2
in this field, etc SOMEHOW in this wording.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, i would be more explicit in tags that are supported. One can reference go constants as valid ones, but specify them explicitly.
There will always be variants that are not yet specified or relevant for go, but do make sense to be explicit for container images that contain code that was written in other languages. For example, whilst GOARM64 is already defined, it doesn't actually do anything different in go - but it does for gcc for example.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The table below does include explicit examples, though 😅
Putting these links here because I keep wanting them and having to find them again (will maybe update this over time with more interesting/useful links):
|
This changes the table to be a line per ISA instead of per variant; adds x86-64, POWER8+, and RISC-V; and notes the appropriate "Go analog" in each case (because these values mirror Go's choices, like our use of
GOOS
andGOARCH
).Of particular note,
GOARM64
andGORISCV64
are not fully implemented or released in Go yet, but they are accepted proposals with in-progress implementations or already merged to main:GOARM64
: all: add GOARM64=v8.1 and so on golang/go#60905GORISCV64
: all: add GORISCV64 environment variable golang/go#61476 (comment)Closes #852