public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Michael Hudson-Doyle <michael.hudson@canonical.com>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [RFC] build-many-glibcs: Add a rv64gcbv-on-rv64gc/lp64d sub-variant
Date: Tue, 23 Apr 2024 15:08:11 +1200	[thread overview]
Message-ID: <CAJ8wqtd0C2ic6P_nWZHYJpxHWOe3nasUa8bQy2MNWrXmX07jgQ@mail.gmail.com> (raw)
In-Reply-To: <mhng-4d3ee592-9f72-4950-b658-ad13293b01e7@palmer-ri-x1c9a>

[-- Attachment #1: Type: text/plain, Size: 2318 bytes --]

On Wed, 17 Apr 2024 at 06:12, Palmer Dabbelt <palmer@rivosinc.com> wrote:

> 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?


Well having the non baseline builds tested and so not having everything
explode as/when we shift the baseline would probably help, yes :-)


> I think we're all a bit worried about being stuck with a very small
> baseline and thus a bunch of vendor-specific behavior.


Yes. That would be unfortunate.


> 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.
>

I think for Ubuntu we are obviously not interested in supporting every
RISC-V core out there, we are only going to be aiming for what would be a
"cortex a" CPU in the ARM world and I think the baseline for those is
probably going to be a bit more than just rv64gc (like, we could almost
certainly just copy Google's baseline for Android).


> 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.
>

We certainly don't have any concrete plans beyond "we don't want to be
stuck on rv64gc forever". We also don't want to be building every package
in Ubuntu for every core either! It's obviously hard to see where things
are going but I can imagine a world where there are different baselines for
different application domains in practice (e.g. iot, routers, servers) with
different baselines in practice and it's worth building some core packages
to target those. But who knows!

Cheers,
mwh

  parent reply	other threads:[~2024-04-23  3:08 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
2024-04-17  9:46     ` Florian Weimer
2024-04-23  3:08     ` Michael Hudson-Doyle [this message]
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=CAJ8wqtd0C2ic6P_nWZHYJpxHWOe3nasUa8bQy2MNWrXmX07jgQ@mail.gmail.com \
    --to=michael.hudson@canonical.com \
    --cc=libc-alpha@sourceware.org \
    --cc=palmer@rivosinc.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).