Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Paul Burton <paul.burton@imgtec.com>,
	Kernel Build Reports Mailman List 
	<kernel-build-reports@lists.linaro.org>,
	"kernelci.org bot" <bot@kernelci.org>,
	"open list:RALINK MIPS ARCHITECTURE" <linux-mips@linux-mips.org>
Subject: Re: next/master build: 212 builds: 3 failed, 209 passed, 384 errors, 58 warnings (next-20170824)
Date: Fri, 25 Aug 2017 13:16:33 +0200	[thread overview]
Message-ID: <20170825111633.GD7433@linux-mips.org> (raw)
In-Reply-To: <CAK8P3a3G8Mo7qsgnbEXNHzU9MRRCppWhBgAT4DF-z3xgiK+WLA@mail.gmail.com>

On Fri, Aug 25, 2017 at 12:19:17AM +0200, Arnd Bergmann wrote:

> On Thu, Aug 24, 2017 at 12:01 PM, kernelci.org bot <bot@kernelci.org> wrote:
> >
> > next/master build: 212 builds: 3 failed, 209 passed, 384 errors, 58 warnings (next-20170824)
> > Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20170824/
> > Tree: next
> > Branch: master
> > Git Describe: next-20170824
> > Git Commit: 9506597de2cde02d48c11d5c250250b9143f59f7
> > Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > Built: 4 unique architectures
> >
> > Build Failures Detected:
> >
> > mips: gcc version 6.3.0 (GCC)
> > cavium_octeon_defconfig FAIL
> > decstation_defconfig FAIL
> > jmr3927_defconfig FAIL
> 
> We currently get three build failures on linux-next, all on MIPS, and
> caused by the same patch series from Paul Burton if I read this right:
> 
> > cavium_octeon_defconfig (mips) — FAIL, 378 errors, 0 warnings, 0 section mismatches
> >
> > Errors:
> > arch/mips/kernel/octeon_switch.S:19: Error: unrecognized opcode `leaf(resume)'
> > arch/mips/kernel/octeon_switch.S:21: Error: invalid operands `mfc0 t1,CP0_STATUS'
> > arch/mips/kernel/octeon_switch.S:22: Error: unrecognized opcode `long_s t1,THREAD_STATUS(a0)'
> > arch/mips/kernel/octeon_switch.S:23: Error: unrecognized opcode `cpu_save_nonscratch a0'
> > ...
> 
> Apparently caused by dc2dd0508e19 ("MIPS: Move r4k FP code from
> r4k_switch.S to r4k_fpu.S")
> 
> > decstation_defconfig (mips) — FAIL, 3 errors, 0 warnings, 0 section mismatches
> >
> > Errors:
> > arch/mips/kernel/r2300_fpu.S:40: Error: unrecognized opcode `export_symbol(_save_fp)'
> > arch/mips/kernel/r2300_fpu.S:41: Error: unrecognized opcode `fpu_save_single $4,$9'
> > arch/mips/kernel/r2300_fpu.S:49: Error: unrecognized opcode `fpu_restore_single $4,$9'
> 
> Same for jmr3927_defconfig, both caused by 4e967a53718f ("MIPS: Move r2300
> FP code from r2300_switch.S to r2300_fpu.S").
> 
> I have no idea what exactly causes the problem. Paul, can you have a look?

My name may not be Paul but I fixed it anyway :)

  Ralf

  parent reply	other threads:[~2017-08-25 11:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <599ea3e4.b785df0a.aff31.4380@mx.google.com>
2017-08-24 22:19 ` next/master build: 212 builds: 3 failed, 209 passed, 384 errors, 58 warnings (next-20170824) Arnd Bergmann
2017-08-24 22:19   ` Arnd Bergmann
2017-08-25 11:16   ` Ralf Baechle [this message]
2017-08-25 11:16     ` Ralf Baechle

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=20170825111633.GD7433@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=arnd@arndb.de \
    --cc=bot@kernelci.org \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linux-mips@linux-mips.org \
    --cc=paul.burton@imgtec.com \
    /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