From: Artur Sinila <logarithmus.dev@gmail.com>
To: "Martin Liška" <mliska@suse.cz>, gcc-patches@gcc.gnu.org
Cc: "H.J. Lu" <hjl.tools@gmail.com>, Jan Hubicka <hubicka@ucw.cz>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] Generalize -fuse-ld= to support absolute path or arbitrary ld.linker
Date: Mon, 28 Jun 2021 16:41:06 +0300 [thread overview]
Message-ID: <82b4d041991a98522e6b62145a2f47e5a51a42e1.camel@logarithmus.dev> (raw)
In-Reply-To: <244b04d4-34ae-087d-7851-068ed1a7b307@suse.cz>
On Mon, 2021-06-28 at 15:26 +0200, Martin Liška wrote:
> On 6/28/21 2:24 PM, Artur Sinila wrote:
> > On Mon, 2021-06-28 at 14:08 +0200, Martin Liška wrote:
> > > On 6/26/21 4:44 PM, Artur Sinila wrote:
> > > > Not so gentle ping :)
> > > > What should happen in order for this patch to be accepted?
> > > >
> > >
> > > Hello.
> > >
> > > We came up to conclusion that one can use the currently supported
> > > option
> > > -fuse-ld={bfd,gold,lld} with -B that can point to an arbitrary
> > > path
> > > the such linker is expected.
> > >
> > > Cheers,
> > > Martin
> >
> > Hello.
> >
> > Thank you for the reply. I'd like to use mold linker with gcc:
> > https://github.com/rui314/mold. So your solution doesn't help.
>
> Well, kind of works. You only need to create a symlink called
> ld which will point to your linker (plus using -B argument as
> mentioned).
>
> >
> > There are 2 options:
> > 1. Add mold to -fuse-ld option
> > 2. Implement --ld-path
> >
> > The 2nd option is much more future-proof: you won't need to add new
> > -fuse-ld variant each time new linker comes up. To provide some
> > context: clang had been supporting passing path to -fuse-ld, but
> > since
> > clang 12 this is deprecated in favor of new --ld-path option. I
> > think
> > we should take an example from clang and implement this useful
> > feature
> > in gcc as well.
>
> Can you please provide a pointer for the deprecation.
> I'm adding Jakub who recommended using the -B argument.
>
> Martin
>
> >
> > Cheers,
> > Artur Sinila
> >
>
See https://reviews.llvm.org/D83015. Speaking about -B option, AFAIK it
will make gcc to search for collect2, cc and other tools in specified
directory, so apart from creating a symlink to mold, I'll also need to
create symlinks to all those tools. Didn't try it in practice though.
Best regards,
Artur Sinila
next prev parent reply other threads:[~2021-06-28 13:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-26 14:44 Artur Sinila
2021-06-28 12:08 ` Martin Liška
2021-06-28 12:24 ` Artur Sinila
2021-06-28 13:26 ` Martin Liška
2021-06-28 13:41 ` Artur Sinila [this message]
2021-06-28 13:49 ` Jakub Jelinek
2021-06-28 13:46 ` Jakub Jelinek
-- strict thread matches above, loose matches on Subject: below --
2020-02-10 0:02 Fangrui Song via gcc-patches
2020-02-13 17:59 ` Fangrui Song via gcc-patches
2020-02-24 23:02 ` Fangrui Song via gcc-patches
2020-03-11 12:55 ` Martin Liška
2020-04-05 22:32 ` Fangrui Song
2020-04-06 7:18 ` Martin Liška
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=82b4d041991a98522e6b62145a2f47e5a51a42e1.camel@logarithmus.dev \
--to=logarithmus.dev@gmail.com \
--cc=freesoftware@logarithmus.dev \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=hubicka@ucw.cz \
--cc=jakub@redhat.com \
--cc=mliska@suse.cz \
/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).