public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rui314 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/104708] RV64: gcc does not pass all library directories to linker Date: Sun, 27 Feb 2022 08:11:03 +0000 [thread overview] Message-ID: <bug-104708-4-8VZuveyOxo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104708-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104708 --- Comment #1 from Rui Ueyama <rui314 at gmail dot com> --- Here is the link to the original bug report: https://github.com/rui314/mold/issues/358
next prev parent reply other threads:[~2022-02-27 8:11 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-27 7:26 [Bug c++/104708] New: " rui314 at gmail dot com 2022-02-27 8:11 ` rui314 at gmail dot com [this message] 2022-02-27 8:17 ` [Bug c++/104708] " pinskia at gcc dot gnu.org
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=bug-104708-4-8VZuveyOxo@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).