From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [OpenWrt-Devel] ARMv4 (not v4t) marked obsolete in gcc-6
Date: Tue, 15 Mar 2016 23:00:05 +0100 [thread overview]
Message-ID: <6978344.h5qhGc4ZP2@wuerfel> (raw)
In-Reply-To: <CAKv+Gu-jHrnpkhE-TzA9FXd_tfm0kLKihXH9SpUcexsqEtmsWQ@mail.gmail.com>
On Tuesday 15 March 2016 21:26:08 Ard Biesheuvel wrote:
> On 15 March 2016 at 16:59, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Friday 11 March 2016 17:56:12 Hans Ulli Kroll wrote:
> >> On Fri, 11 Mar 2016, Roman Yeryomin wrote:
> > diff --git a/arch/arm/Makefile b/arch/arm/Makefile
> > index 9fb3fee0e908..3c312d37a83a 100644
> > --- a/arch/arm/Makefile
> > +++ b/arch/arm/Makefile
> > @@ -19,6 +19,11 @@ LDFLAGS_vmlinux += --be8
> > LDFLAGS_MODULE += --be8
> > endif
> >
> > +ifeq ($(CONFIG_CPU_32v4),y)
> > +LDFLAGS_vmlinux += $(call ld-option,--fix-v4bx)
> > +LDFLAGS_MODULE += $(call ld-option,--fix-v4bx)
>
> Does this have any effect on partial linking? I would expect the
> module loader to handle the R_ARM_V4BX relocation in this case
I have checked that the recursive linking stages don't need it for
the built-in files, only the final link step for vmlinux does.
For loadable modules, the loader indeed applies the same fix,
and apparently also does this on ARMv4T and ARMv5 machines even
when it's not needed there. I think for consistency it makes
sense to set the flag for both vmlinux and modules (as we
do for --be8).
Arnd
next prev parent reply other threads:[~2016-03-15 22:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 9:13 ARMv4 (not v4t) marked obsolete in gcc-6 Arnd Bergmann
2016-03-10 9:31 ` Russell King - ARM Linux
2016-03-10 16:59 ` Arnd Bergmann
2016-03-10 17:09 ` Russell King - ARM Linux
2016-03-10 17:59 ` Arnd Bergmann
2016-03-10 9:38 ` Dmitry Eremin-Solenikov
2016-03-10 16:38 ` Arnd Bergmann
2016-03-10 21:49 ` Dmitry Eremin-Solenikov
2016-03-15 15:14 ` Arnd Bergmann
2016-03-10 9:40 ` Baruch Siach
2016-03-10 10:58 ` Robin Murphy
2016-03-10 15:40 ` Dave Martin
2016-03-11 5:44 ` Hans Ulli Kroll
2016-03-11 6:48 ` [OpenWrt-Devel] " John Crispin
2016-03-11 16:09 ` Roman Yeryomin
2016-03-11 16:56 ` Hans Ulli Kroll
2016-03-15 15:59 ` Arnd Bergmann
2016-03-15 17:01 ` John Crispin
2016-03-15 20:26 ` Ard Biesheuvel
2016-03-15 22:00 ` Arnd Bergmann [this message]
2016-03-17 16:18 ` Ramana Radhakrishnan
2016-03-17 19:34 ` Dmitry Eremin-Solenikov
2016-03-18 13:25 ` Ramana Radhakrishnan
2016-03-21 20:50 ` Arnd Bergmann
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=6978344.h5qhGc4ZP2@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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