From: "Andreas K. Hüttel" <dilfridge@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/riscv:master commit in: eclass/
Date: Sun, 28 Apr 2019 10:24:02 +0000 (UTC) [thread overview]
Message-ID: <1556447014.b42744dd8d41b9a471b0f99fe8d9e7cb8f806a9a.dilfridge@gentoo> (raw)
commit: b42744dd8d41b9a471b0f99fe8d9e7cb8f806a9a
Author: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 28 10:23:34 2019 +0000
Commit: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
CommitDate: Sun Apr 28 10:23:34 2019 +0000
URL: https://gitweb.gentoo.org/proj/riscv.git/commit/?id=b42744dd
eclass: filter -march in gcc build for riscv
Signed-off-by: Andreas K. Hüttel <dilfridge <AT> gentoo.org>
eclass/toolchain.eclass | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/eclass/toolchain.eclass b/eclass/toolchain.eclass
index be94db8..ff66986 100644
--- a/eclass/toolchain.eclass
+++ b/eclass/toolchain.eclass
@@ -1513,6 +1513,11 @@ gcc_do_filter_flags() {
# dont want to funk ourselves
filter-flags '-mabi*' -m31 -m32 -m64
+ # on riscv, only specific combinations of march and mabi work... so we need
+ # to strip both and trust the compiler to do the right thing, otherwise
+ # multilib build fails
+ [[ $(tc-arch) == riscv* ]] && filter-flags '-march*'
+
filter-flags -frecord-gcc-switches # 490738
filter-flags -mno-rtm -mno-htm # 506202
next reply other threads:[~2019-04-28 10:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-28 10:24 Andreas K. Hüttel [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-11 16:14 [gentoo-commits] proj/riscv:master commit in: eclass/ Andreas K. Hüttel
2020-09-05 20:50 Andreas K. Hüttel
2020-09-05 20:50 Andreas K. Hüttel
2020-09-02 19:39 Andreas K. Hüttel
2020-09-02 19:39 Andreas K. Hüttel
2019-05-03 21:55 Andreas K. Hüttel
2019-04-28 20:56 Andreas K. Hüttel
2019-04-28 20:09 Andreas K. Hüttel
2019-04-28 19:49 Andreas K. Hüttel
2019-04-28 10:00 Andreas K. Hüttel
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=1556447014.b42744dd8d41b9a471b0f99fe8d9e7cb8f806a9a.dilfridge@gentoo \
--to=dilfridge@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@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