RISC-V toolchain: --print-libgcc-file-name is wrong [407786163]

Assigned

Bug

Status Update

No update yet.

Description

to...@google.com

created issue #1

Apr 1, 2025 06:13PM

Zephyr and EC using the --print-libgcc-file-name flag to get the path to the compiler_rt library. For the RISC-V toolchain, the path printed is incorrect:

CROSTC_USER_ACKNOWLEDGES_THAT_RISCV_IS_EXPERIMENTAL=1 riscv32-cros-elf-clang --print-libgcc-file-name

/usr/lib64/clang/20/lib/riscv32-cros-unknown-elf/libclang_rt.builtins.a

The correct path is:

/usr/lib64/clang/20/lib/baremetal/libclang_rt.builtins-riscv32.a

Comments

to...@google.com <to...@google.com> #2Apr 1, 2025 06:16PM

Any fix planned ?

bl...@google.com <bl...@google.com> #3Apr 1, 2025 06:32PM

Assigned to in...@google.com.

Can u give me info of tablet ? I know who had it unlocked with my info on
it ! I'll make sure I thank her later,thanks for the info.if there anything
I can help this group within here if I can help,keep me in mind !
E.C.
C.h.e.s.
ecastillo041979@gmail.com

On Wed, May 26, 2021, 6:44 AM <buganizer-system@google.com> wrote:

- Show quoted text -

Issue 407786163

Description

Issue summary

Comments

to...@google.com <to...@google.com> #2Apr 1, 2025 06:16PM

bl...@google.com <bl...@google.com> #3Apr 1, 2025 06:32PM

Add comment

Issue metadata