From: Nathan Chancellor <nathan@kernel.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
llvm@lists.linux.dev, Nick Desaulniers <ndesaulniers@google.com>,
patches@lists.linux.dev, Nathan Chancellor <nathan@kernel.org>,
Paul Mackerras <paulus@samba.org>, Tom Rix <trix@redhat.com>,
linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 0/2] Link the PowerPC vDSO with ld.lld
Date: Mon, 9 May 2022 13:46:33 -0700 [thread overview]
Message-ID: <20220509204635.2539549-1-nathan@kernel.org> (raw)
Hi all,
This series is an alternative to the one proposed by Nick before the
PowerPC vDSO unification in commit fd1feade75fb ("powerpc/vdso: Merge
vdso64 and vdso32 into a single directory"):
https://lore.kernel.org/20200901222523.1941988-1-ndesaulniers@google.com/
Normally, we try to make compiling and linking two separate stages so
that they can be done by $(CC) and $(LD) respectively, which is more in
line with what the user expects, versus using the compiler as a linker
driver and relying on the implicit default linker value. However, as
shown in the above thread, getting this right for the PowerPC vDSO is a
little tricky due to the linker emulation values.
The unification might make this easier but that needs further
investigation. To avoid regressing ld.bfd while enabling support for
linking the vDSO with ld.lld, we can tell the compiler to use ld.lld via
either '--ld-path=' (clang 12.0.0) or '-fuse-ld=lld'.
The first patch avoids a warning from ld.lld when linking both vDSO
objects and the second patch adds the flags.
This should help avoid the issue noticed during Alexey's LTO bring up:
https://lore.kernel.org/CAKwvOdmUMhqhQhDCpWjMNiQQPvwOJB9MbUkF3RR0BL+H+DagmA@mail.gmail.com/
Nathan Chancellor (2):
powerpc/vdso: Remove unused ENTRY in linker scripts
powerpc/vdso: Link with ld.lld when requested
arch/powerpc/kernel/vdso/Makefile | 1 +
arch/powerpc/kernel/vdso/vdso32.lds.S | 1 -
arch/powerpc/kernel/vdso/vdso64.lds.S | 1 -
3 files changed, 1 insertion(+), 2 deletions(-)
base-commit: f06351f8c0c85e2d53e73c53a33b4ef55b4ad6de
--
2.36.1
next reply other threads:[~2022-05-09 20:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 20:46 Nathan Chancellor [this message]
2022-05-09 20:46 ` [PATCH 1/2] powerpc/vdso: Remove unused ENTRY in linker scripts Nathan Chancellor
2022-05-09 21:05 ` Nick Desaulniers
2022-05-10 6:22 ` Alexey Kardashevskiy
2022-05-10 6:41 ` Fangrui Song
2022-05-09 20:46 ` [PATCH 2/2] powerpc/vdso: Link with ld.lld when requested Nathan Chancellor
2022-05-09 21:24 ` Nick Desaulniers
2022-05-09 21:47 ` Nathan Chancellor
2022-05-09 21:58 ` Nick Desaulniers
2022-05-09 22:30 ` Nathan Chancellor
2022-05-10 6:22 ` Alexey Kardashevskiy
2022-05-10 16:25 ` Nathan Chancellor
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=20220509204635.2539549-1-nathan@kernel.org \
--to=nathan@kernel.org \
--cc=aik@ozlabs.ru \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=llvm@lists.linux.dev \
--cc=mpe@ellerman.id.au \
--cc=ndesaulniers@google.com \
--cc=patches@lists.linux.dev \
--cc=paulus@samba.org \
--cc=trix@redhat.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 NNTP newsgroup(s).