From: Nick Desaulniers <ndesaulniers@google.com>
To: Stefan Agner <stefan@agner.ch>
Cc: Nathan Chancellor <natechancellor@gmail.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Russell King <linux@armlinux.org.uk>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Nicolas Pitre <nicolas.pitre@linaro.org>
Subject: Re: [PATCH 2/2] ARM: Wrap '--pic-veneer' with ld-option
Date: Mon, 7 Jan 2019 11:42:36 -0800 [thread overview]
Message-ID: <CAKwvOdk-YkXtOKs0SFc3=pEyoe5FaeNqW-JhJii6u34HUvdDNA@mail.gmail.com> (raw)
In-Reply-To: <9f43145527aa4220ecde4c3b263241e6@agner.ch>
On Sat, Dec 29, 2018 at 4:27 AM Stefan Agner <stefan@agner.ch> wrote:
>
> On 05.12.2018 20:45, Nathan Chancellor wrote:
> > On Wed, Dec 05, 2018 at 07:39:55PM +0100, Ard Biesheuvel wrote:
> >> On Wed, 5 Dec 2018 at 19:36, Nathan Chancellor <natechancellor@gmail.com> wrote:
> >> >
> >> > On Wed, Dec 05, 2018 at 09:09:56AM +0100, Ard Biesheuvel wrote:
> >> > > (+ 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?
Just for the list, 2 patches to lld:
https://github.com/ClangBuiltLinux/linux/issues/286#issuecomment-452027802
--
Thanks,
~Nick Desaulniers
next prev parent reply other threads:[~2019-01-07 19:42 UTC|newest]
Thread overview: 24+ 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 ` [PATCH 2/2] ARM: Wrap '--pic-veneer' with ld-option Nathan Chancellor
2018-12-05 7:37 ` Ard Biesheuvel
2018-12-05 8:06 ` Nathan Chancellor
2018-12-05 8:09 ` Ard Biesheuvel
2018-12-05 18:21 ` Nick Desaulniers
2018-12-05 19:30 ` Peter Smith
2018-12-05 18:36 ` Nathan Chancellor
2018-12-05 18:39 ` Ard Biesheuvel
2018-12-05 18:41 ` Nick Desaulniers
2018-12-05 22:59 ` Stefan Agner
2018-12-05 23:19 ` Nick Desaulniers
2018-12-05 19:45 ` Nathan Chancellor
2018-12-05 21:03 ` Ard Biesheuvel
2018-12-29 12:27 ` Stefan Agner
2019-01-07 19:42 ` Nick Desaulniers [this message]
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 16:37 ` Nicolas Pitre
2018-12-05 17:47 ` Nick Desaulniers
2018-12-29 12:49 ` Stefan Agner
2018-12-31 18:12 ` [PATCH v2] " Nathan Chancellor
2019-01-05 16:34 ` Nicolas Pitre
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='CAKwvOdk-YkXtOKs0SFc3=pEyoe5FaeNqW-JhJii6u34HUvdDNA@mail.gmail.com' \
--to=ndesaulniers@google.com \
--cc=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=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: 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).