All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Mark Brown <broonie@kernel.org>
Cc: kernel-build-reports@lists.linaro.org, linux-mips@linux-mips.org
Subject: Re: next build: 198 builds: 4 failed, 194 passed, 7 errors, 82 warnings (next-20161214)
Date: Fri, 16 Dec 2016 01:56:06 +0100	[thread overview]
Message-ID: <20161216005606.GD15191@linux-mips.org> (raw)
In-Reply-To: <20161214135214.osrlldhxvxzfwial@sirena.org.uk>

On Wed, Dec 14, 2016 at 01:52:14PM +0000, Mark Brown wrote:

> > mips:    gcc version 5.3.0 (Sourcery CodeBench Lite 2016.05-8)
> > 
> >     allnoconfig: FAIL
> >     generic_defconfig: FAIL
> >     ip27_defconfig: FAIL
> >     tinyconfig: FAIL
> 
> These MIPS builds have been failing in kernelci ever since MIPS was
> added.  This means that we've got a constant level of noise in the
> results which makes them less useful for everyone - people get used to
> ignoring errors.  Is there any plan to get these fixed?

I had to "bisect" binutils versions to hit the allnoconfig and tinyconfig
build issues.  Turns out it's a problem specific to binutils 2.25 which
when generating 32 bit ELF does not permit the use of 64 bit constants,
not even when explicitly to the 64 bit instruction set, for example:

	.set	mips3
	dli	$1, 0x9000000080000000

The only fix I was able to find that will work with all binutils, is
open coding the dli macro instruction as

	li	$1, 0x9000
	dsll	$1, $1, 48

Which is pretty much what the assembler should have generated from the dli
anyway.

  Ralf

  parent reply	other threads:[~2016-12-16  0:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <58510536.04c7190a.4a2fb.ae5c@mx.google.com>
2016-12-14 13:52 ` next build: 198 builds: 4 failed, 194 passed, 7 errors, 82 warnings (next-20161214) Mark Brown
2016-12-14 16:06   ` Ralf Baechle
2016-12-14 17:45     ` Mark Brown
2016-12-14 20:56       ` Arnd Bergmann
2016-12-14 20:56         ` Arnd Bergmann
2016-12-15  3:22       ` Ralf Baechle
2016-12-15  8:02         ` Arnd Bergmann
2016-12-15 11:00         ` Mark Brown
2016-12-16  0:56   ` Ralf Baechle [this message]
2016-12-16 12:19     ` Mark Brown

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=20161216005606.GD15191@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=broonie@kernel.org \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linux-mips@linux-mips.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.