public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "i at maskray dot me" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/93645] Support Clang 12 --ld-path=
Date: Wed, 22 Dec 2021 19:16:19 +0000 [thread overview]
Message-ID: <bug-93645-4-uisAK8SsOs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93645-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93645
--- Comment #13 from Fangrui Song <i at maskray dot me> ---
(In reply to Martin Liška from comment #12)
> (In reply to Fangrui Song from comment #11)
> > (In reply to Martin Liška from comment #10)
> > > I replied here:
> > > https://gcc.gnu.org/pipermail/gcc-patches/2021-June/573823.html
> >
> > There are people wanting to use mold
> > https://www.reddit.com/r/rust/comments/rhcnzt/
> > mold_a_modern_linker_10_release/
>
> I agree that's unfortunate. Note I'm having a patch that adds -fuse-ld=mold:
> https://gcc.gnu.org/git/?p=gcc.git;a=commit;
> h=759cdbb29dbe8fc80ba5c1f113a015cafe9eb69c
>
> I can try suggesting that to the community for GCC 12 (and maybe backport
> that).
> Are you interested?
I think it may be useful to simply allow -fuse-ld=word (`word` cannot include a
separator).
If that may be troublesome, having -fuse-ld=mold in GCC 12 is still nice.
--ld-path is occasionally useful, but I can accept that GCC declines it.
> Note the linker is very interesting, but it lacks LTO support..
Right...
next prev parent reply other threads:[~2021-12-22 19:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-93645-4@http.gcc.gnu.org/bugzilla/>
2020-03-11 12:33 ` [Bug driver/93645] Support -fuse-ld=/absolute/path/to/ld marxin at gcc dot gnu.org
2020-05-07 11:56 ` jakub at gcc dot gnu.org
2020-07-23 6:52 ` rguenth at gcc dot gnu.org
2020-07-25 6:02 ` [Bug driver/93645] Support Clang 12 --ld-path= i at maskray dot me
2020-09-17 18:12 ` i at maskray dot me
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-06-25 21:20 ` hjl.tools at gmail dot com
2021-06-25 21:24 ` pinskia at gcc dot gnu.org
2021-06-26 14:27 ` freesoftware at logarithmus dot dev
2021-06-28 12:09 ` marxin at gcc dot gnu.org
2021-12-22 9:06 ` i at maskray dot me
2021-12-22 9:16 ` marxin at gcc dot gnu.org
2021-12-22 19:16 ` i at maskray dot me [this message]
2021-12-28 13:12 ` marxin at gcc dot gnu.org
2021-12-28 17:54 ` i at maskray dot me
2021-12-29 11:48 ` marxin at gcc dot gnu.org
2022-06-28 10:39 ` jakub at gcc dot gnu.org
2023-07-07 8:46 ` rguenth 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-93645-4-uisAK8SsOs@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: link
Be 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).