From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: <linux-snps-arc@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jeff Moyer <jmoyer@redhat.com>,
"Alexey Brodkin" <Alexey.Brodkin@synopsys.com>
Subject: Re: Build failure in linux mainline when building arcv2 images
Date: Fri, 29 Jul 2016 13:03:56 -0700 [thread overview]
Message-ID: <66774d12-285a-438f-c050-fba65601bd3c@synopsys.com> (raw)
In-Reply-To: <579B5D79.8060907@roeck-us.net>
On 07/29/2016 06:43 AM, Guenter Roeck wrote:
> On 07/28/2016 10:20 PM, Vineet Gupta wrote:
>> Hi Guenter,
>>
>> On 07/28/2016 08:23 PM, Guenter Roeck wrote:
>>> Hi Vineet,
>>>
>>> Mainline fails to build arcv2 images with the following error.
>>>
>>> {standard input}: Assembler messages:
>>> {standard input}:19174: Error: Instruction with long immediate data in delay slot
>>> make[2]: *** [block/cfq-iosched.o] Error 1
>>>
>>> Bisect points to commit 9a7f38c42c2 ("cfq-iosched: Convert from jiffies to
>>> nanoseconds"),
>>> but I don't really hold it responsible. It looks more like a compiler / binutils
>>> problem
>>> to me.
>>
>> Indeed - triggers a latent bug in ARC gcc !
>>
>>> I am using a toolchain built with buildroot (gcc 4.8.3). Is there a more recent
>>> toolchain
>>> than the one in buildroot available, by any chance ? If yes, where do I find it ?
>>
>> Yeah there's a 4.8.5 based one (referred to as GNU 2016.03) - will prebuilt
>> toolchain suffice or would you prefer building on your own. Prebuilt could be
>> found below.
>>
>> https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases/tag/arc-2016.03
>>
>>
>> For building on your own, Alexey can point to upstream buildroot which enabled
>> 2016.03 tools.
>>
>
> Unfortunately, I get the same error when using "arc-linux-gcc.br_real (Buildroot
> 2016.05) 4.8.5".
Weird - I don't see this when building mainline of now using prebuilt 2016.03
tools on github . I'm building axs103_smp_defconfig.
What exact buildroot commit did u use to build your tools BTW - I can try and
replicate that here !
Thx,
-Vineet
next prev parent reply other threads:[~2016-07-29 20:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 3:23 Build failure in linux mainline when building arcv2 images Guenter Roeck
2016-07-29 5:20 ` Vineet Gupta
2016-07-29 13:43 ` Guenter Roeck
2016-07-29 20:03 ` Vineet Gupta [this message]
2016-07-29 21:48 ` Guenter Roeck
2016-07-29 22:46 ` Vineet Gupta
2016-07-30 4:27 ` Guenter Roeck
2016-08-01 9:53 ` Alexey Brodkin
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=66774d12-285a-438f-c050-fba65601bd3c@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=linux@roeck-us.net \
/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;
as well as URLs for NNTP newsgroup(s).