From: "Andreas K. Hüttel" <dilfridge@gentoo.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org
Subject: Re: RISC-V 64bit and 32bit binaries on the same system
Date: Mon, 07 Sep 2020 20:05:22 +0300 [thread overview]
Message-ID: <12603168.s5MMGUR32x@farino> (raw)
In-Reply-To: <alpine.DEB.2.21.2009071653280.18581@digraph.polyomino.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]
> > 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)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2020-09-07 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 13:32 Andreas K. Hüttel
2020-09-07 16:56 ` Joseph Myers
2020-09-07 17:05 ` Andreas K. Hüttel [this message]
2020-09-09 4:22 ` Palmer Dabbelt
2020-09-09 19:49 ` Andreas K. Hüttel
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=12603168.s5MMGUR32x@farino \
--to=dilfridge@gentoo.org \
--cc=joseph@codesourcery.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).