From: Stafford Horne <shorne@gmail.com>
To: GLIBC patches <libc-alpha@sourceware.org>
Cc: Linux OpenRISC <linux-openrisc@vger.kernel.org>,
Stafford Horne <shorne@gmail.com>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: [PATCH v3 3/3] build-many-glibcs.py: Add openrisc hard float glibc variant
Date: Fri, 3 May 2024 18:27:31 +0100 [thread overview]
Message-ID: <20240503172731.675178-4-shorne@gmail.com> (raw)
In-Reply-To: <20240503172731.675178-1-shorne@gmail.com>
This adds the OpenRISC hard float glibc variant to the build many
script. We update the compiler for glibc to support hard-float
multilibs to allow us to use a single generic compiler for all glibc
variants, this requires updating the compiler name.
Tested and all builds are passing.
Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
---
Since v2:
- No change
Since v1:
- No change
scripts/build-many-glibcs.py | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/scripts/build-many-glibcs.py b/scripts/build-many-glibcs.py
index 35dac538e5..38eb9f2dd2 100755
--- a/scripts/build-many-glibcs.py
+++ b/scripts/build-many-glibcs.py
@@ -362,8 +362,9 @@ class Context(object):
gcc_cfg=['--enable-obsolete'])
self.add_config(arch='or1k',
os_name='linux-gnu',
- variant='soft',
- gcc_cfg=['--with-multilib-list=mcmov'])
+ gcc_cfg=['--with-multilib-list=mcmov,mhard-float'],
+ glibcs=[{'variant': 'soft'},
+ {'variant': 'hard', 'ccopts': '-mhard-float'}])
self.add_config(arch='powerpc',
os_name='linux-gnu',
gcc_cfg=['--disable-multilib', '--enable-secureplt'],
--
2.44.0
prev parent reply other threads:[~2024-05-03 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 17:27 [PATCH v3 0/3] OpenRISC glibc hard float support Stafford Horne
2024-05-03 17:27 ` [PATCH v3 1/3] or1k: Add hard float libm-test-ulps Stafford Horne
2024-05-03 17:27 ` [PATCH v3 2/3] or1k: Add hard float support Stafford Horne
2024-05-03 17:27 ` Stafford Horne [this message]
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=20240503172731.675178-4-shorne@gmail.com \
--to=shorne@gmail.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-openrisc@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).