This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: RISC-V ELF multilibs
- From: Jim Wilson <jimw at sifive dot com>
- To: Matthew Fortune <Matthew dot Fortune at mips dot com>
- Cc: Palmer Dabbelt <palmer at sifive dot com>, "sebastian dot huber at embedded-brains dot de" <sebastian dot huber at embedded-brains dot de>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Thu, 31 May 2018 12:28:34 -0700
- Subject: Re: RISC-V ELF multilibs
- References: <e4e6d066-5ef0-d421-ac32-29455907bc00@sifive.com> <mhng-bb9024b6-8178-4256-b19f-af50a894c694@palmer-si-x1c4> <b9d6704a0c0b431a81f29b8c5b0ef521@mips.com>
On Thu, May 31, 2018 at 7:23 AM, Matthew Fortune
<Matthew.Fortune@mips.com> wrote:
> I do actually have a solution for this but it is not submitted upstream.
> MIPS has basically the same set of problems that RISC-V does in this area
> and in an ideal world there would be no 'fallback' multilib such that if
> you use compiler options that map to a library variant that does not
> exist then the linker just fails to find any libraries at all rather than
> using the default multilib.
>
> I can share the raw patch for this and try to give you some idea about how
> it works. I am struggling to find time to do much open source support at
> the moment so may not be able to do all the due diligence to get it
> committed. Would you be willing to take a look and do some of the work to
> get it in tree?
I have a long list of things on my to do list. RISC-V is a new
target, and there is lots of stuff that needs to be bug fixed,
finished, or added. I can't make any guarantees.
But if you file a bug report and then attach a patch to it, someone
might volunteer to help finish it. Or if it is too big to be
reasonably attached to a bug report (like the nano mips work) you
could put it on a branch, and mention the branch name as unfinished
work in a bug report.
Jim