From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev@lists.ozlabs.org, Paul Mackerras <paulus@samba.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc: Disable RELOCATABLE for COMPILE_TEST with PPC64
Date: Mon, 30 Jun 2014 19:22:08 -0700 [thread overview]
Message-ID: <53B21B50.2010207@roeck-us.net> (raw)
In-Reply-To: <20140701105510.75718b47@canb.auug.org.au>
On 06/30/2014 05:55 PM, Stephen Rothwell wrote:
> Hi Guenter,
>
> On Mon, 30 Jun 2014 11:45:30 -0700 Guenter Roeck <linux@roeck-us.net> wrote:
>>
>> powerpc:allmodconfig has been failing for some time with the following
>> error.
>>
>> arch/powerpc/kernel/exceptions-64s.S: Assembler messages:
>> arch/powerpc/kernel/exceptions-64s.S:1312: Error: attempt to move .org backwards
>> make[1]: *** [arch/powerpc/kernel/head_64.o] Error 1
>>
>> A number of attempts to fix the problem by moving around code have been
>> unsuccessful and resulted in failed builds for some configurations and
>> the discovery of toolchain bugs.
>>
>> Fix the problem by disabling RELOCATABLE for COMPILE_TEST builds instead.
s/Fix/Work around/
would probably be a better here.
>> While this is less than perfect, it avoids substantial code changes
>> which would otherwise be necessary just to make COMPILE_TEST builds
>> happy and might have undesired side effects.
>>
>> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
>
> I'll dump this in my "fixes" tree today and see how it goes.
>
Would be great. Note that allyescconfig still fails with relocation errors
after this patch has been applied.
Thanks,
Guenter
next prev parent reply other threads:[~2014-07-01 2:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 18:45 [PATCH] powerpc: Disable RELOCATABLE for COMPILE_TEST with PPC64 Guenter Roeck
2014-07-01 0:55 ` Stephen Rothwell
2014-07-01 2:22 ` Guenter Roeck [this message]
2014-07-04 19:51 ` Guenter Roeck
2014-07-08 3:03 ` Guenter Roeck
2014-07-08 3:10 ` Benjamin Herrenschmidt
2014-07-13 6:02 ` Nick Krause
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=53B21B50.2010207@roeck-us.net \
--to=linux@roeck-us.net \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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