From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [signal:master 62/63] arch/m68k/kernel/entry.S:115: Error: operands mismatch -- statement `movem
Date: Sat, 08 Sep 2012 16:28:17 +0000 [thread overview]
Message-ID: <20120908162817.GA26297@localhost> (raw)
In-Reply-To: <20120908135733.GA25549@localhost>
On Sat, Sep 08, 2012 at 03:54:49PM +0100, Al Viro wrote:
> On Sat, Sep 08, 2012 at 09:57:33PM +0800, Fengguang Wu wrote:
> > Hi Al,
> >
> > FYI, kernel build failed on
> >
> > tree: git://git.kernel.org/pub/scm/linux/kernel/git/viro/signal.git master
> > head: aad206fddcb7642e6777b1b992645299b7557ded
> > commit: 28ba6e34ce54cb7ce2e509369a6f9c47c13083d9 [62/63] m68k: switch to generic sys_execve()/kernel_execve()
> > config: m68k-m5475evb_defconfig (attached as .config)
> >
> > All related error/warning messages:
> >
> > arch/m68k/kernel/entry.S: Assembler messages:
> > arch/m68k/kernel/entry.S:115: Error: operands mismatch -- statement `moveml (%sp)+,%d0-%d2' ignored
> > arch/m68k/kernel/entry.S:117: Error: operands mismatch -- statement `moveml %d1-%d3,-(%sp)' ignored
>
> On which toolchain? It had been a valid instruction on all m68k, starting with
> 68000. Is that as(1) insisting on %sp@+ form instead of (%sp)+? But we have
> both kinds used in arch/m68k, so if some toolchain version barfs on that, it's
> probably rather unhappy elsewhere...
Err, I'm running binaries from:
https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.6.3/x86_64-gcc-4.6.3-nolibc_m68k-linux.tar.xz
Thanks,
Fengguang
next prev parent reply other threads:[~2012-09-08 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-08 13:57 [signal:master 62/63] arch/m68k/kernel/entry.S:115: Error: operands mismatch -- statement `moveml (% Fengguang Wu
2012-09-08 14:54 ` [signal:master 62/63] arch/m68k/kernel/entry.S:115: Error: operands mismatch -- statement `movem Al Viro
2012-09-08 16:28 ` Fengguang Wu [this message]
2012-09-08 17:48 ` Al Viro
2012-09-08 19:58 ` Al Viro
2012-09-09 2:31 ` Al Viro
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=20120908162817.GA26297@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).