All of lore.kernel.org
 help / color / mirror / Atom feed
From: linux@roeck-us.net (Guenter Roeck)
To: linux-snps-arc@lists.infradead.org
Subject: Build failure in linux mainline when building arcv2 images
Date: Thu, 28 Jul 2016 20:23:18 -0700	[thread overview]
Message-ID: <579ACC26.9020106@roeck-us.net> (raw)

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.

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 ?

Thanks,
Guenter

WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux@roeck-us.net>
To: Vineet Gupta <vgupta@synopsys.com>
Cc: linux-snps-arc@lists.infradead.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jeff Moyer <jmoyer@redhat.com>
Subject: Build failure in linux mainline when building arcv2 images
Date: Thu, 28 Jul 2016 20:23:18 -0700	[thread overview]
Message-ID: <579ACC26.9020106@roeck-us.net> (raw)

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.

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 ?

Thanks,
Guenter

             reply	other threads:[~2016-07-29  3:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29  3:23 Guenter Roeck [this message]
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  5:20   ` Vineet Gupta
2016-07-29 13:43   ` Guenter Roeck
2016-07-29 13:43     ` Guenter Roeck
2016-07-29 20:03     ` Vineet Gupta
2016-07-29 20:03       ` Vineet Gupta
2016-07-29 21:48       ` Guenter Roeck
2016-07-29 21:48         ` Guenter Roeck
2016-07-29 22:46         ` Vineet Gupta
2016-07-29 22:46           ` Vineet Gupta
2016-07-30  4:27           ` Guenter Roeck
2016-07-30  4:27             ` Guenter Roeck
2016-08-01  9:53             ` Alexey Brodkin
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=579ACC26.9020106@roeck-us.net \
    --to=linux@roeck-us.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.