public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/104708] New: RV64: gcc does not pass all library directories to linker
@ 2022-02-27 7:26 rui314 at gmail dot com
2022-02-27 8:11 ` [Bug c++/104708] " rui314 at gmail dot com
2022-02-27 8:17 ` pinskia at gcc dot gnu.org
0 siblings, 2 replies; 3+ messages in thread
From: rui314 at gmail dot com @ 2022-02-27 7:26 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104708
Bug ID: 104708
Summary: RV64: gcc does not pass all library directories to
linker
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: rui314 at gmail dot com
Target Milestone: ---
I'm the author of the mold linker (https://github.com/rui314/mold).
As far as I know, gcc always passes all library paths to the linker by -L<dir>,
but I got a bug report that that's not the case on RV64. It is reported that
gcc does not pass some obvious paths such as `-L/usr` or `-L/usr/lib`.
Can gcc pass all library paths to the linker on RV64?
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-02-27 8:17 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-27 7:26 [Bug c++/104708] New: RV64: gcc does not pass all library directories to linker rui314 at gmail dot com
2022-02-27 8:11 ` [Bug c++/104708] " rui314 at gmail dot com
2022-02-27 8:17 ` pinskia at gcc dot gnu.org
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).