From: Palmer Dabbelt <palmer@rivosinc.com>
To: michael.hudson@canonical.com
Cc: libc-alpha@sourceware.org
Subject: Re: [RFC] build-many-glibcs: Add a rv64gcbv-on-rv64gc/lp64d sub-variant
Date: Tue, 16 Apr 2024 11:12:52 -0700 (PDT) [thread overview]
Message-ID: <mhng-4d3ee592-9f72-4950-b658-ad13293b01e7@palmer-ri-x1c9a> (raw)
In-Reply-To: <CAJ8wqtekk4fE2aeCTPj47AynCKq_f+ExFLPv6FFNXB8jw6P-aQ@mail.gmail.com>
On Tue, 16 Apr 2024 00:01:31 PDT (-0700), michael.hudson@canonical.com wrote:
> On Tue, 16 Apr 2024 at 07:28, Palmer Dabbelt <palmer@rivosinc.com> wrote:
>
>> Unfortunately I don't think we can drop support for the other base ISAs:
>> the distros appear to be targeting rv64gc and that's the only common
>> base for most hardware that's out there.
>>
>
> This is certainly the case for Ubuntu for now but I certainly hope that by
> 26.04 we are able to be a bit more aggressive here, fwiw.
That'd be awesome. Any idea if something like this would help?
I think we're all a bit worried about being stuck with a very small
baseline and thus a bunch of vendor-specific behavior. That's certainly
the way things are trending right now in RISC-V land, it's already super
complicated to manage and it looks like it's going to get worse before
it gets better.
If we can pick up some extra testing burden now as a way to reduce
fragmentation then it's probably a win in the long run, even if we have
to go through a few generations of this before things calm down. If
you're planning on moving to something completely different, though,
then maybe it's not worth the extra builds.
> Cheers,
> mwh
next prev parent reply other threads:[~2024-04-16 18:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 19:24 Palmer Dabbelt
2024-04-15 20:05 ` enh
2024-04-15 20:22 ` Palmer Dabbelt
2024-04-25 5:11 ` Jeff Law
2024-04-15 20:24 ` Darius Rad
2024-04-15 21:36 ` Palmer Dabbelt
2024-04-16 14:55 ` Darius Rad
2024-04-16 16:04 ` Palmer Dabbelt
2024-04-16 20:41 ` Darius Rad
2024-04-16 21:06 ` Palmer Dabbelt
2024-04-16 7:01 ` Michael Hudson-Doyle
2024-04-16 18:12 ` Palmer Dabbelt [this message]
2024-04-17 9:46 ` Florian Weimer
2024-04-23 3:08 ` Michael Hudson-Doyle
2024-04-17 10:26 ` Florian Weimer
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=mhng-4d3ee592-9f72-4950-b658-ad13293b01e7@palmer-ri-x1c9a \
--to=palmer@rivosinc.com \
--cc=libc-alpha@sourceware.org \
--cc=michael.hudson@canonical.com \
/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).