RISC-V 64bit and 32bit binaries on the same system

[Andreas K. Hüttel]

> > gcc and glibc build and install fine. However, there's a fundamental
> > problem with this configuration. ld.so does not filter by ELFCLASS (as it
> > does, e.g., for x64-64 vs i686), and the order of directories in the
> > dynamic linker config determines e.g. which libstdc++ a binary sees
> > first. [#]
> 
> Whenever I asked about such configurations, the answer was always that the
> Linux kernel port did not support running RV32I processes on RV64I
> processors, although the architecture definition supported it as an
> optional feature.  I don't know if that Linux kernel support has since
> been implemented.

Not to my knowledge.

> <https://sourceware.org/legacy-ml/libc-alpha/2018-01/msg00008.html> is
> where I described what you need to do in glibc to support that kind of
> configuration for an architecture.

Yeah, that's the more knowledgeable answer compared to my newbie digging at 
what is needed. 

(And it looks like a comparatively large amount of work for a situation that 
is right now fairly hypothetical, unless you try silly things with qemu like 
me).

So maybe the multilib defaults of gcc should be changed?

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer 
(council, qa, toolchain, base-system, perl, libreoffice)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: This is a digitally signed message part.
URL: <https://sourceware.org/pipermail/libc-alpha/attachments/20200907/d1c109e4/attachment.sig>