public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@rivosinc.com>
To: libc-alpha@sourceware.org
Cc: Palmer Dabbelt <palmer@rivosinc.com>
Subject: [PATCH] build-many-glibcs: Add a RISC-V config with most of the B extensions
Date: Wed,  6 Sep 2023 08:06:06 -0700	[thread overview]
Message-ID: <20230906150605.10221-2-palmer@rivosinc.com> (raw)

We've had some B-related string optimizaitons show up over the past
year, but we don't have a configuration in build-many-glibcs that tests
them.  This adds Zba, Zbc, and Zbs -- it doesn't add Zbc, but IIUC
that's the common configuration.  To avoid blowing up the build count it
just adds rv64/lp64d.

Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
---
I haven't tested this at all, but figured I'd send it up for comments.
I'm not really sure what the bar should be for builds here, we kind of
just started with everything and then didn't add any more.
---
 scripts/build-many-glibcs.py | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/scripts/build-many-glibcs.py b/scripts/build-many-glibcs.py
index 3082522140..bbc153831e 100755
--- a/scripts/build-many-glibcs.py
+++ b/scripts/build-many-glibcs.py
@@ -396,6 +396,11 @@ class Context(object):
                         variant='rv64imafdc-lp64d',
                         gcc_cfg=['--with-arch=rv64imafdc', '--with-abi=lp64d',
                                  '--disable-multilib'])
+        self.add_config(arch='riscv64',
+                        os_name='linux-gnu',
+                        variant='rv64imafdcb-lp64d',
+                        gcc_cfg=['--with-arch=rv64imafdc_zba_zbb_zbs', '--with-abi=lp64d',
+                                 '--disable-multilib'])
         self.add_config(arch='s390x',
                         os_name='linux-gnu',
                         glibcs=[{},
-- 
2.42.0


             reply	other threads:[~2023-09-06 15:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-06 15:06 Palmer Dabbelt [this message]
2023-09-06 20:43 ` Florian Weimer
2023-09-07 15:24   ` Palmer Dabbelt
2023-09-07 15:50     ` Florian Weimer
2023-09-07 16:39       ` Palmer Dabbelt
2023-09-07 17:00         ` Evan Green
2023-09-07 17:05           ` Palmer Dabbelt

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=20230906150605.10221-2-palmer@rivosinc.com \
    --to=palmer@rivosinc.com \
    --cc=libc-alpha@sourceware.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).