From: Iain Sandoe <iains.gcc@gmail.com>
Cc: "Andrew Pinski (QUIC)" <quic_apinski@quicinc.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
David Edelsohn <dje.gcc@gmail.com>,
Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Subject: Re: Request for testing on non-Linux targets; remove special casing of /usr/lib and /lib from the driver
Date: Wed, 17 Apr 2024 15:33:54 +0100 [thread overview]
Message-ID: <E5BBA339-B771-44F7-A5DF-CFEC5BC3CE5A@gmail.com> (raw)
In-Reply-To: <ydd4jc0ay4x.fsf@CeBiTec.Uni-Bielefeld.DE>
Hi Andrew,
> On 17 Apr 2024, at 14:59, Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> wrote:
>> The driver currently will remove "/lib" and "/usr/lib" from the library
>> path that gets passed to the linker because it considers them as paths that
>> the linker will already known to search. But this is not true for newer
>> linkers, mold and lld for an example don't have a default search path.
>> This patch removes the special casing to fix FreeBSD building where lld is
>> used by default and also fix riscv-linux-gnu when used in combination with
>> mold.
>> I have tested it on x86_64-linux-gnu and it works there but since the code
>> in the driver has been around since 1992, I request some folks to test it
>> on AIX, Mac OS (Darwin) and solaris where the ld is not GNU bfd ld as I
>> don't have access to those targets currently.
>
> actually, you do: all of those are availble inside the cfarm.
>
> I've also tested the patch on i386-pc-solaris2.11 and
> sparc-sun-solaris2.11 with the native ld: no regressions in either case.
I tested so far on x86_64 darwin, but the behaviour of collect2 is the same
for all arches. Actually, I do not see any difference in behaviour when looking
at the -Wl,-v output (it seems that somehow those paths are not currently
pruned for Darwin; if I add -L /lib to the command line on a GCC build without
this patch it is passed through despite that it’s non-existent). However, that’s
a separate bug, perhaps.
So - as far as this patch is concerned it seems OK for Darwin,
Iain
next prev parent reply other threads:[~2024-04-17 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 23:47 Andrew Pinski (QUIC)
2024-04-17 13:59 ` Rainer Orth
2024-04-17 14:33 ` Iain Sandoe [this message]
2024-04-19 17:01 ` David Edelsohn
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=E5BBA339-B771-44F7-A5DF-CFEC5BC3CE5A@gmail.com \
--to=iains.gcc@gmail.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=quic_apinski@quicinc.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).