From: Ard Biesheuvel <ard.biesheuvel@linaro.org> To: Nathan Chancellor <natechancellor@gmail.com>, Arnd Bergmann <arnd@arndb.de> Cc: Russell King <linux@armlinux.org.uk>, linux-arm-kernel <linux-arm-kernel@lists.infradead.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Stefan Agner <stefan@agner.ch>, Nicolas Pitre <nicolas.pitre@linaro.org>, Nick Desaulniers <ndesaulniers@google.com> Subject: Re: [PATCH 2/2] ARM: Wrap '--pic-veneer' with ld-option Date: Wed, 5 Dec 2018 09:09:56 +0100 [thread overview] Message-ID: <CAKv+Gu9Nq51Fj_14MYS6MEm0VPHOJB1CBFkCHmyC8Wt0=NWpRg@mail.gmail.com> (raw) In-Reply-To: <20181205080645.GA11936@flashbox> (+ Arnd) On Wed, 5 Dec 2018 at 09:06, Nathan Chancellor <natechancellor@gmail.com> wrote: > > On Wed, Dec 05, 2018 at 08:37:05AM +0100, Ard Biesheuvel wrote: > > On Wed, 5 Dec 2018 at 02:42, Nathan Chancellor <natechancellor@gmail.com> wrote: > > > > > > This flag is not supported by lld: > > > > > > ld.lld: error: unknown argument: --pic-veneer > > > > > > Signed-off-by: Nathan Chancellor <natechancellor@gmail.com> > > > > Hi Nate, > > > > Does this mean ld.lld is guaranteed to produce position independent > > veneers if you build kernels that are bigger than the typical range of > > a relative branch? > > > > Hi Ard, > > Honestly, I'm not quite sure. I saw your commit that introduced this > flag and I wasn't quite sure what to make of it for lld. What > configuration would I use to verify and what would I check for? > Try building allyesconfig, and check the resulting binary for veneers (which have 'veneer' in the symbol name, at least when ld.bfd emits them). These veneers should not take the [virtual] address of the branch target directly, but take a PC relative offset (as in the example in the commit log of that patch you are referring to) > Additionally, I have filed an LLVM bug for the lld developers to > check and see if this is a flag they should support: > > https://bugs.llvm.org/show_bug.cgi?id=39886 > > Thanks for the quick reply, > Nathan > > > > --- > > > arch/arm/Makefile | 2 +- > > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > > > diff --git a/arch/arm/Makefile b/arch/arm/Makefile > > > index e2a0baf36766..4fab2aa29570 100644 > > > --- a/arch/arm/Makefile > > > +++ b/arch/arm/Makefile > > > @@ -10,7 +10,7 @@ > > > # > > > # Copyright (C) 1995-2001 by Russell King > > > > > > -LDFLAGS_vmlinux := --no-undefined -X --pic-veneer > > > +LDFLAGS_vmlinux := --no-undefined -X $(call ld-option,--pic-veneer) > > > ifeq ($(CONFIG_CPU_ENDIAN_BE8),y) > > > LDFLAGS_vmlinux += --be8 > > > KBUILD_LDFLAGS_MODULE += --be8 > > > -- > > > 2.20.0.rc1 > > >
WARNING: multiple messages have this Message-ID (diff)
From: Ard Biesheuvel <ard.biesheuvel@linaro.org> To: Nathan Chancellor <natechancellor@gmail.com>, Arnd Bergmann <arnd@arndb.de> Cc: Nicolas Pitre <nicolas.pitre@linaro.org>, Nick Desaulniers <ndesaulniers@google.com>, Russell King <linux@armlinux.org.uk>, Stefan Agner <stefan@agner.ch>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, linux-arm-kernel <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH 2/2] ARM: Wrap '--pic-veneer' with ld-option Date: Wed, 5 Dec 2018 09:09:56 +0100 [thread overview] Message-ID: <CAKv+Gu9Nq51Fj_14MYS6MEm0VPHOJB1CBFkCHmyC8Wt0=NWpRg@mail.gmail.com> (raw) In-Reply-To: <20181205080645.GA11936@flashbox> (+ Arnd) On Wed, 5 Dec 2018 at 09:06, Nathan Chancellor <natechancellor@gmail.com> wrote: > > On Wed, Dec 05, 2018 at 08:37:05AM +0100, Ard Biesheuvel wrote: > > On Wed, 5 Dec 2018 at 02:42, Nathan Chancellor <natechancellor@gmail.com> wrote: > > > > > > This flag is not supported by lld: > > > > > > ld.lld: error: unknown argument: --pic-veneer > > > > > > Signed-off-by: Nathan Chancellor <natechancellor@gmail.com> > > > > Hi Nate, > > > > Does this mean ld.lld is guaranteed to produce position independent > > veneers if you build kernels that are bigger than the typical range of > > a relative branch? > > > > Hi Ard, > > Honestly, I'm not quite sure. I saw your commit that introduced this > flag and I wasn't quite sure what to make of it for lld. What > configuration would I use to verify and what would I check for? > Try building allyesconfig, and check the resulting binary for veneers (which have 'veneer' in the symbol name, at least when ld.bfd emits them). These veneers should not take the [virtual] address of the branch target directly, but take a PC relative offset (as in the example in the commit log of that patch you are referring to) > Additionally, I have filed an LLVM bug for the lld developers to > check and see if this is a flag they should support: > > https://bugs.llvm.org/show_bug.cgi?id=39886 > > Thanks for the quick reply, > Nathan > > > > --- > > > arch/arm/Makefile | 2 +- > > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > > > diff --git a/arch/arm/Makefile b/arch/arm/Makefile > > > index e2a0baf36766..4fab2aa29570 100644 > > > --- a/arch/arm/Makefile > > > +++ b/arch/arm/Makefile > > > @@ -10,7 +10,7 @@ > > > # > > > # Copyright (C) 1995-2001 by Russell King > > > > > > -LDFLAGS_vmlinux := --no-undefined -X --pic-veneer > > > +LDFLAGS_vmlinux := --no-undefined -X $(call ld-option,--pic-veneer) > > > ifeq ($(CONFIG_CPU_ENDIAN_BE8),y) > > > LDFLAGS_vmlinux += --be8 > > > KBUILD_LDFLAGS_MODULE += --be8 > > > -- > > > 2.20.0.rc1 > > > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-12-05 8:10 UTC|newest] Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-12-05 1:42 [PATCH 1/2] ARM: Remove '-p' from LDFLAGS Nathan Chancellor 2018-12-05 1:42 ` Nathan Chancellor 2018-12-05 1:42 ` [PATCH 2/2] ARM: Wrap '--pic-veneer' with ld-option Nathan Chancellor 2018-12-05 1:42 ` Nathan Chancellor 2018-12-05 7:37 ` Ard Biesheuvel 2018-12-05 7:37 ` Ard Biesheuvel 2018-12-05 8:06 ` Nathan Chancellor 2018-12-05 8:06 ` Nathan Chancellor 2018-12-05 8:09 ` Ard Biesheuvel [this message] 2018-12-05 8:09 ` Ard Biesheuvel 2018-12-05 18:21 ` Nick Desaulniers 2018-12-05 18:21 ` Nick Desaulniers 2018-12-05 19:30 ` Peter Smith 2018-12-05 19:30 ` Peter Smith 2018-12-05 18:36 ` Nathan Chancellor 2018-12-05 18:36 ` Nathan Chancellor 2018-12-05 18:39 ` Ard Biesheuvel 2018-12-05 18:39 ` Ard Biesheuvel 2018-12-05 18:41 ` Nick Desaulniers 2018-12-05 18:41 ` Nick Desaulniers 2018-12-05 22:59 ` Stefan Agner 2018-12-05 22:59 ` Stefan Agner 2018-12-05 23:19 ` Nick Desaulniers 2018-12-05 23:19 ` Nick Desaulniers 2018-12-05 19:45 ` Nathan Chancellor 2018-12-05 21:03 ` Ard Biesheuvel 2018-12-05 21:03 ` Ard Biesheuvel 2018-12-29 12:27 ` Stefan Agner 2018-12-29 12:27 ` Stefan Agner 2019-01-07 19:42 ` Nick Desaulniers 2019-01-07 19:42 ` Nick Desaulniers 2018-12-05 18:40 ` Nick Desaulniers 2018-12-05 18:40 ` Nick Desaulniers 2018-12-05 7:37 ` [PATCH 1/2] ARM: Remove '-p' from LDFLAGS Ard Biesheuvel 2018-12-05 7:37 ` Ard Biesheuvel 2018-12-05 16:37 ` Nicolas Pitre 2018-12-05 16:37 ` Nicolas Pitre 2018-12-05 17:47 ` Nick Desaulniers 2018-12-05 17:47 ` Nick Desaulniers 2018-12-29 12:49 ` Stefan Agner 2018-12-29 12:49 ` Stefan Agner 2018-12-31 18:12 ` [PATCH v2] " Nathan Chancellor 2018-12-31 18:12 ` Nathan Chancellor 2019-01-05 16:34 ` Nicolas Pitre 2019-01-05 16:34 ` Nicolas Pitre 2019-01-07 19:19 ` Nick Desaulniers 2019-01-07 19:19 ` Nick Desaulniers
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='CAKv+Gu9Nq51Fj_14MYS6MEm0VPHOJB1CBFkCHmyC8Wt0=NWpRg@mail.gmail.com' \ --to=ard.biesheuvel@linaro.org \ --cc=arnd@arndb.de \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@armlinux.org.uk \ --cc=natechancellor@gmail.com \ --cc=ndesaulniers@google.com \ --cc=nicolas.pitre@linaro.org \ --cc=stefan@agner.ch \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.