From: James Hogan <james.hogan@mips.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: <linux-kernel@vger.kernel.org>, <linux-metag@vger.kernel.org>
Subject: Re: metag build errors in mainline kernel
Date: Wed, 21 Feb 2018 12:27:19 +0000 [thread overview]
Message-ID: <20180221122719.GI29460@jhogan-linux.mipstec.com> (raw)
In-Reply-To: <20180220234443.GA27059@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]
On Tue, Feb 20, 2018 at 03:44:43PM -0800, Guenter Roeck wrote:
> The following errors are seen when building the kernel with the latest
> available metag toolchain (4.2.4 (IMG-1.4.0.700)). Kernel version tested
> is (v4.16-rc2-64-gaf3e79d29555).
>
> metag:allmodconfig
>
> arch/metag/kernel/devtree.c:54: error: implicit declaration of function 'pr_info'
>
> arch/metag/kernel/perf/perf_event.c:831: error: label ‘out’ used but not defined
> arch/metag/kernel/perf/perf_event.c:822: warning: unused variable ‘cpu’
Thanks, these are easy enough for me to fix up.
>
> metag:meta2_smp_defconfig
>
> kernel/time/hrtimer.c: In function 'hrtimer_run_softirq':
> time/hrtimer.c:1431: error: unable to find a register to spill in class 'Yr_REGS'
> time/hrtimer.c:1431: error: this is the insn:
> (insn:HI 41 40 99 2 kernel/time/hrtimer.c:576 (set (mem/s/j:DI (plus:SI (reg/f:SI 15 D1.7 [orig:84 D.45290 ] [84])
> (const_int 368 [0x170])) [0 <variable>.offset+0 S8 A128])
> (reg:DI 99 [ <variable>.offset ])) 211 {*sto_di_1_1_off12} (nil)
> (expr_list:REG_DEAD (reg:DI 99 [ <variable>.offset ])
> (nil)))
> kernel/time/hrtimer.c:1431: confused by earlier errors, bailing out
Hmm.. ancient shelved toolchain. Perhaps this is the excuse we need to
say goodbye to arch/metag/...
Cheers
James
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-02-21 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 23:44 Guenter Roeck
2018-02-21 12:27 ` James Hogan [this message]
2018-02-21 13:53 ` Graham Whaley
2018-02-21 14:16 ` Guenter Roeck
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=20180221122719.GI29460@jhogan-linux.mipstec.com \
--to=james.hogan@mips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-metag@vger.kernel.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
all inboxes | Powered by JetHome®