From: David Edelsohn <dje.gcc@gmail.com>
To: "Andrew Pinski (QUIC)" <quic_apinski@quicinc.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"iains.gcc@gmail.com" <iains.gcc@gmail.com>
Subject: Re: Request for testing on non-Linux targets; remove special casing of /usr/lib and /lib from the driver
Date: Fri, 19 Apr 2024 13:01:32 -0400 [thread overview]
Message-ID: <CAGWvnymBPZTKOpVBQELTPYgc3M=hodozosY7f05mvRjmxBPcYg@mail.gmail.com> (raw)
In-Reply-To: <DM6PR02MB4058D4FAE319F0F9B10BFC82B8082@DM6PR02MB4058.namprd02.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
The patch does not cause failures on AIX. Is it removing explicit
references to /lib and /usr/lib?
It seems more appropriate for GCC 15.
Thanks for alerting me to the patch to test on AIX. AIX is in CFarm.
Thanks David
On Tue, Apr 16, 2024 at 7:49 PM Andrew Pinski (QUIC) <
quic_apinski@quicinc.com> wrote:
> Hi all,
> 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.
>
> Thanks,
> Andrew Pinski
>
prev parent reply other threads:[~2024-04-19 17:01 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
2024-04-19 17:01 ` David Edelsohn [this message]
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='CAGWvnymBPZTKOpVBQELTPYgc3M=hodozosY7f05mvRjmxBPcYg@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iains.gcc@gmail.com \
--cc=quic_apinski@quicinc.com \
/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).