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: Wed, 14 Dec 2016 17:06:09 +0100 [thread overview]
Message-ID: <20161214160609.GA15191@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:
> On Wed, Dec 14, 2016 at 12:39:18AM -0800, kernelci.org bot 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 wonder if these are also toolchain-related issues. allnoconfig and
tinyconfig do build fine for me with GCC 6.1.0 and binutils 2.26.20160125.
generic_defconfig requires mkimage of uboot-tools or it will fail like this:
ITB arch/mips/boot/vmlinux.gz.itb
"mkimage" command not found - U-Boot images will not be built
arch/mips/boot/Makefile:159: recipe for target 'arch/mips/boot/vmlinux.gz.itb' failed
make[1]: *** [arch/mips/boot/vmlinux.gz.itb] Error 1
arch/mips/Makefile:365: recipe for target 'vmlinux.gz.itb' failed
make: *** [vmlinux.gz.itb] Error 2
ip27_defconfig indeed has a build issue but it's new for 4.9 (commit
3ffc17d8768be705e292ac4c2e3ab1f18dc06047 ("MIPS: Adjust MIPS64 CAC_BASE to
reflect Config.K0")). And with that patch reverted GCC 6.1.0 blows up with
an internal compilter error:
CC [M] drivers/net/ethernet/qlogic/qlge/qlge_main.o
drivers/net/ethernet/qlogic/qlge/qlge_main.c: In function ‘qlge_probe’:
drivers/net/ethernet/qlogic/qlge/qlge_main.c:4812:1: error: insn does not satisfy its constraints:
}
^
(insn 1373 1371 1361 79 (parallel [
(set (reg/f:DI 3 $3 [490])
(symbol_ref:DI ("delayed_work_timer_fn") [flags 0x241] <function_decl 0x7fdb8658ed20 delayed_work_timer_fn>))
(clobber (scratch:DI))
]) drivers/net/ethernet/qlogic/qlge/qlge_main.c:4690 287 {*lea64}
(nil))
drivers/net/ethernet/qlogic/qlge/qlge_main.c:4812:1: internal compiler error: in extract_constrain_insn, at recog.c:2190
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
GCC 6.2.0 dies the same way.
What binutils are you using and can you send me the build errors messages?
Thanks,
Ralf
next prev parent reply other threads:[~2016-12-14 16:06 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 [this message]
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
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=20161214160609.GA15191@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox