public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Nicholas Piggin <npiggin@gmail.com>,
	Nicolas Pitre <nicolas.pitre@linaro.org>,
	linux-arch@vger.kernel.org,
	Segher Boessenkool <segher@kernel.crashing.org>,
	Alan Modra <amodra@gmail.com>,
	linux-kbuild@vger.kernel.org,
	Russell King <linux@armlinux.org.uk>,
	Julian Brown <julian@codesourcery.com>,
	Michal Marek <mmarek@suse.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH] arm: add an option for erratum 657417
Date: Fri, 26 Aug 2016 16:07:49 +0200	[thread overview]
Message-ID: <201608261607.49610.arnd@arndb.de> (raw)
In-Reply-To: <20160826211729.592ff5cd@roar.ozlabs.ibm.com>

On Friday 26 August 2016, Nicholas Piggin wrote:
> > I still see a problem with big-endian builds failing with
> > thinarc/gc-sections, I'll investigate that some other day,
> > or you could have a look at that if you want to make sure
> > it's an ARM specific problem, not something with your
> > patches in general.
> > 
> > The patch that I sent for enabling the two on ARM blocks
> > out CONFIG_CPU_BIG_ENDIAN, so just revert that hunk to see
> > the problem. It's possible that it only breaks when doing
> > a big-endian build after a little-endian build without
> > a "make clean" inbetween.
> 
> I'm able to build big endian ARM allyesconfig with thin
> archives and gc-sections, worked fine.
> 
> There have been a few bugs in powerpc when failing to notice
> the change when endian of builds was swapped, so maybe you
> got bitten by something similar.

I tracked this down as well now, and it's also a problem on my
local machine, your patches are fine. In order to debug
the other problem, I was building with
"make LD=/home/arnd/..../ld" to try out different
versions of the linker, and that caused the "LD += -EB"
line from arch/arm/Makefile to be ignored.

We should probably override LDFLAGS rather than LD
(and AFLAGS instead of AS) for big-endian builds, but
that is unrelated to your work.

	Arnd

      reply	other threads:[~2016-08-26 14:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-12  8:19 [PATCH] arm: add an option for erratum 657417 Nicholas Piggin
2016-08-12 12:33 ` Russell King - ARM Linux
2016-08-12 13:15   ` Nicholas Piggin
2016-08-12 13:49     ` Ard Biesheuvel
2016-08-12 13:50       ` Ard Biesheuvel
2016-08-12 13:52         ` Russell King - ARM Linux
2016-08-12 13:54           ` Ard Biesheuvel
2016-08-12 13:51       ` Russell King - ARM Linux
2016-08-12 14:17   ` Robin Murphy
2016-08-12 14:23     ` Russell King - ARM Linux
2016-08-12 14:32       ` Russell King - ARM Linux
2016-08-23 12:01 ` Arnd Bergmann
2016-08-24  4:00   ` Nicholas Piggin
2016-08-24  7:41     ` Arnd Bergmann
2016-08-24  9:05       ` Nicholas Piggin
2016-08-24 10:56         ` Nicholas Piggin
2016-08-24 12:06           ` Nicholas Piggin
2016-08-24 15:01           ` Arnd Bergmann
2016-08-26 11:17             ` Nicholas Piggin
2016-08-26 14:07               ` Arnd Bergmann [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=201608261607.49610.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=amodra@gmail.com \
    --cc=julian@codesourcery.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mmarek@suse.com \
    --cc=nicolas.pitre@linaro.org \
    --cc=npiggin@gmail.com \
    --cc=sam@ravnborg.org \
    --cc=segher@kernel.crashing.org \
    --cc=sfr@canb.auug.org.au \
    /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