From: will.deacon@arm•com (Will Deacon)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] arm64: vdso: work-around broken ELF toolchains in Makefile
Date: Fri, 19 Jun 2015 15:55:44 +0100 [thread overview]
Message-ID: <20150619145544.GA8173@arm.com> (raw)
In-Reply-To: <55842B92.4090702@mentor.com>
On Fri, Jun 19, 2015 at 03:47:46PM +0100, Nathan Lynch wrote:
> On 06/19/2015 07:56 AM, Will Deacon wrote:
> > When building the kernel with a bare-metal (ELF) toolchain, the -shared
> > option may not be passed down to collect2, resulting in silent corruption
> > of the vDSO image (in particular, the DYNAMIC section is omitted).
>
> I checked arch/arm with
>
> arm-none-eabi-gcc (Fedora 4.9.2-3.fc21) 4.9.2
>
> and it doesn't seem to be affected. Do you know whether the toolchain
> issue is aarch64-specific?
I don't know for sure, but it seems to affect all AArch64 toolchains so
from your observations, arch/arm/ should be ok.
Will
prev parent reply other threads:[~2015-06-19 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 12:56 [PATCH] arm64: vdso: work-around broken ELF toolchains in Makefile Will Deacon
2015-06-19 14:10 ` Catalin Marinas
2015-06-19 14:47 ` Nathan Lynch
2015-06-19 14:55 ` Will Deacon [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=20150619145544.GA8173@arm.com \
--to=will.deacon@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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