public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/104707] GCC doesn't give default lib path to the linker when multilib is off Date: Wed, 10 Apr 2024 11:13:00 +0000 [thread overview] Message-ID: <bug-104707-4-ZW36U8zjUg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104707-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104707 --- Comment #10 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Note multilib is not the issue. See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97304#c14 for more analysis of the issue (I think there might be another bug report talking about this too).
next prev parent reply other threads:[~2024-04-10 11:13 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-27 5:34 [Bug target/104707] New: gcc on riscv64 isn't passing entire library path to the linker sterprim at outlook dot com 2022-02-27 5:41 ` [Bug target/104707] " pinskia at gcc dot gnu.org 2022-02-27 8:17 ` pinskia at gcc dot gnu.org 2022-04-19 10:33 ` jpalus+gcc at fastmail dot com 2022-04-19 11:00 ` pinskia at gcc dot gnu.org 2022-04-19 11:36 ` jpalus+gcc at fastmail dot com 2023-04-03 6:32 ` [Bug other/104707] GCC doesn't give default lib path to the linker when multilib is off sterprim at outlook dot com 2023-04-03 6:36 ` pinskia at gcc dot gnu.org 2023-04-03 6:58 ` [Bug driver/104707] " i at rvalue dot moe 2023-04-03 7:01 ` pinskia at gcc dot gnu.org 2024-04-10 11:13 ` pinskia at gcc dot gnu.org [this message] 2024-04-16 19:06 ` 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-104707-4-ZW36U8zjUg@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).