-
Notifications
You must be signed in to change notification settings - Fork 275
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
Improve CI (Aarch64, Power) #285
Conversation
local -r GCC_PREFIX="powerpc64" | ||
;; | ||
"ppc") | ||
#local -r POWER_URL="https://toolchains.bootlin.com/downloads/releases/toolchains/powerpc-e500mc/tarballs/powerpc-e500mc--glibc--stable-2021.11-1.tar.bz2" |
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.
Why is it commented out?
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.
While QEmu provide a single ppc
target (as well as docker), bootlin provide several flavors
440fp
and e500mc
for PowerPC while here I arbitrarily the 440fp
we could have choose the other one...
An other way would be to have ppc-e500mc
and ppc-440fp
(and ppc
alias of ppc-440fp
?)
ref:
docker run --rm --privileged multiarch/qemu-user-static --reset -p yes
...
Setting /usr/bin/qemu-ppc-static as binfmt interpreter for ppc
Setting /usr/bin/qemu-ppc64-static as binfmt interpreter for ppc64
Setting /usr/bin/qemu-ppc64le-static as binfmt interpreter for ppc64le
note: same issue with ppc64[le]
: power8
, e5500
, 'e6500', le-power8
...
@@ -230,12 +253,14 @@ function expand_codescape_config() { | |||
"mips64") | |||
MIPS_FLAGS="-EB -mips64r6 -mabi=64" | |||
FLAVOUR="mips-r6-hard" | |||
#MIPS_FLAGS="-EB -mips64r2 -mabi=64" |
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.
same here and below, why do you need to keep these comments?
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.
same here maybe we could have a flag to decide which version to use so user can easily reuse this script to target the correct CPU by just changing one line, so while we only enable one flavor it's easy for the community to adapt.
Or again we should/could have both mips-r6
/mips-r2
and a mips
alias to target the last one aka mips-r6
?
Few updates