On Wed, Apr 24, 2024 at 2:16 PM Florian Weimer <fweimer@xxxxxxxxxx> wrote: > > * Andrea Bolognani: > > > Wouldn't changing -mabi effectively make the result a new Fedora > > architecture? IIUC, binaries built with -mabi=lp64d wouldn't be able > > to load libraries built with -mabi=lp64dv and vice versa. > > > > If that's correct, then we can't simply have a single "riscv64" > > architecture: instead, we need to call what we have today > > riscv64_lp64d, and be ready for riscv64_lp64dv as well as whatever > > comes next. > > Right. > > > It would be somewhat similar to existing architectures that can be > > used in both Little-Endian (ppc64le) and Big-Endian (ppc64) modes. > > With different paths, it would be more like i686 and x86_64. That is, > you can build and run software for both variants from the same operating > system image. That's not the case for ppc64 and ppc64le. When we started Fedora/RISCV years ago we didn't want to things: - multilib - CONFIG_COMPAT So it's one ABI per arch string. CONFIG_COMPAT is limited to a single company effort (T-HEAD), and I haven't seen or heard about it being used in general. I would assume a new ABI would mean a new arch string. There are some arch strings floating around from FreeBSD and OpenEmbedded (OE) that aren't common: riscv64sf (FreeBSD, soft floats, might have been removed recently), riscv64nf (OE, -mabi=lp64), riscv64nc (OE, C extension disabled). lp64dv is not currently being discussed for toolchains, and what it means. There might be more ABIs because of other extensions arriving thus it might not be only about the vectors standard vs calling conventions (I really don't like these names). I just want to remind you that "rv64gc" + "lp64d" combination will be quite a restrictive combination within a few years, but we are probably 1-3 years away from that discussion. > > > This is quite different from just bumping the ISA baseline, where > > existing binaries and libraries are still usable in the new > > environment. > > Right, changing the vector calling convention may change the size of > jmp_buf, and then you have a new ABI even if use of the vector features > is optional. > > Thanks, > Florian > -- > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
