From: mpe@ellerman.id.au (Michael Ellerman)
To: linux-snps-arc@lists.infradead.org
Subject: Build regressions/improvements in v4.9-rc1
Date: Wed, 19 Oct 2016 22:50:40 +1100 [thread overview]
Message-ID: <87inso4kxb.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <9a0f80b3-adb3-36de-d59f-885ac29ea2e6@synopsys.com>
Vineet Gupta <Vineet.Gupta1 at synopsys.com> writes:
> On 10/17/2016 02:02 PM, Arnd Bergmann wrote:
>> On Monday, October 17, 2016 9:59:24 AM CEST Vineet Gupta wrote:
>>> On 10/17/2016 12:34 AM, Geert Uytterhoeven wrote:
>>>>> 48 error regressions:
>>>>>> + /home/kisskb/slave/src/arch/arc/include/asm/atomic.h: Error: bad instruction `llockd r2,[r0]': => 476
>>>>>> + /home/kisskb/slave/src/arch/arc/include/asm/atomic.h: Error: bad instruction `llockd r2,[r13]': => 475
>>>
>>> [snip...]
>>>
>>>>>> + /home/kisskb/slave/src/arch/arc/include/asm/atomic.h: Error: bad instruction `scondd r4,[r8]': => 516
>>>>>> + /home/kisskb/slave/src/arch/arc/include/asm/atomic.h: Error: bad instruction `scondd r6,[r3]': => 478
>>>> arcv2/axs103_smp_defconfig
>
> @Michael can I bother you to upgrade the tools or is this absolutely must for you.
Happy to, just short on time.
I tried building a new toolchain with buildroot, using the instructions
from last time, but the resulting toolchain doesn't relocate, ie. it has
hard-coded paths in it. Any ideas?
cheers
next prev parent reply other threads:[~2016-10-19 11:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1476688913-15648-1-git-send-email-geert@linux-m68k.org>
2016-10-17 7:34 ` Build regressions/improvements in v4.9-rc1 Geert Uytterhoeven
2016-10-17 16:59 ` Vineet Gupta
2016-10-17 21:02 ` Arnd Bergmann
2016-10-17 22:37 ` Vineet Gupta
2016-10-19 11:50 ` Michael Ellerman [this message]
2016-10-19 12:23 ` Alexey Brodkin
2016-10-19 20:32 ` Thomas Petazzoni
2016-10-26 23:56 ` Michael Ellerman
2016-10-27 7:07 ` Thomas Petazzoni
2016-10-27 9:07 ` Alexey Brodkin
2016-10-27 9:11 ` Thomas Petazzoni
2016-10-27 9:24 ` Geert Uytterhoeven
2016-10-27 9:39 ` Alexey Brodkin
2016-10-27 17:21 ` Vineet Gupta
2016-10-28 10:42 ` Arnd Bergmann
2016-10-27 9:32 ` Arnd Bergmann
2016-10-27 10:04 ` Thomas Petazzoni
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=87inso4kxb.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linux-snps-arc@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