From: Georgy Yakovlev <gyakovlev@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Cc: Georgy Yakovlev <gyakovlev@gentoo.org>
Subject: [gentoo-catalyst] [PATCH 2/3] arch/ppc.toml: don't force -mabi=elfv2 on power subarches.
Date: Tue, 20 Oct 2020 21:33:46 -0700 [thread overview]
Message-ID: <20201021043347.632763-2-gyakovlev@gentoo.org> (raw)
In-Reply-To: <20201021043347.632763-1-gyakovlev@gentoo.org>
-mabi=elfv2 is default on ppc64le in gcc/glibc toolchain for all
powerpc64le-*-linux-gnu CHOSTS, so we don't need to pass it.
forcing -mabi=elfv2 on ppc64(be) is quite risky, as it's not standard
configuration and not officialy supported by glibc at all.
according to glibc upstream it should be a separate ABI port.
Also many apps/tools assume elfv1 on big-endian, and while fixes are
being upstreamed, we've observed breakage in: openssl[asm], nodejs,
ffmpeg and others.
If we want to ship elfv2 ppc64be stage,
we should define it as separate subarch and strictly put it in experimental.
to my knowledge those subarch definitions are not used by releng yet, so
we will not break anything.
Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
---
arch/ppc.toml | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/ppc.toml b/arch/ppc.toml
index 870c7647..6f74789d 100644
--- a/arch/ppc.toml
+++ b/arch/ppc.toml
@@ -23,22 +23,22 @@ CHOST = "powerpc64-unknown-linux-gnu"
USE = [ "altivec", "ibm",]
[ppc64.power7]
-COMMON_FLAGS = "-O2 -pipe -mcpu=power7 -mtune=power7 -mabi=elfv2"
+COMMON_FLAGS = "-O2 -pipe -mcpu=power7 -mtune=power7"
CHOST = "powerpc64-unknown-linux-gnu"
USE = [ "altivec", "ibm",]
[ppc64.power7le]
-COMMON_FLAGS = "-O2 -pipe -mcpu=power7 -mtune=power7 -mabi=elfv2"
+COMMON_FLAGS = "-O2 -pipe -mcpu=power7 -mtune=power7"
CHOST = "powerpc64le-unknown-linux-gnu"
USE = [ "altivec", "ibm",]
[ppc64.power8]
-COMMON_FLAGS = "-O2 -pipe -mcpu=power8 -mtune=power8 -mabi=elfv2"
+COMMON_FLAGS = "-O2 -pipe -mcpu=power8 -mtune=power8"
CHOST = "powerpc64-unknown-linux-gnu"
USE = [ "altivec", "ibm",]
[ppc64.power8le]
-COMMON_FLAGS = "-O2 -pipe -mcpu=power8 -mtune=power8 -mabi=elfv2"
+COMMON_FLAGS = "-O2 -pipe -mcpu=power8 -mtune=power8"
CHOST = "powerpc64le-unknown-linux-gnu"
USE = [ "altivec", "ibm",]
--
2.29.0
next prev parent reply other threads:[~2020-10-21 4:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 4:33 [gentoo-catalyst] [PATCH 1/3] arch/ppc.toml: add CHOST based subarches Georgy Yakovlev
2020-10-21 4:33 ` Georgy Yakovlev [this message]
2020-10-21 4:33 ` [gentoo-catalyst] [PATCH 3/3] arch/ppc.toml: add power9 subarches Georgy Yakovlev
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=20201021043347.632763-2-gyakovlev@gentoo.org \
--to=gyakovlev@gentoo.org \
--cc=gentoo-catalyst@lists.gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox