From: Stafford Horne <shorne@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
openrisc@lists.librecores.org,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [OpenRISC] Build regressions/improvements in v4.11-rc2
Date: Mon, 13 Mar 2017 23:12:28 +0900 [thread overview]
Message-ID: <20170313141228.GA2418@lianli.shorne-pla.net> (raw)
In-Reply-To: <CAMuHMdUSmQ=9VQX_-U6nfxitwxeBJ950JM-+cO7o+3OqFK=c5g@mail.gmail.com>
On Mon, Mar 13, 2017 at 11:15:23AM +0100, Geert Uytterhoeven wrote:
> On Mon, Mar 13, 2017 at 9:43 AM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
> > JFYI, when comparing v4.11-rc2[1] to v4.11-rc1[3], the summaries are:
> > - build errors: +6/-13
>
> + /home/kisskb/slave/src/arch/openrisc/include/asm/atomic.h: Error:
> /home/kisskb/slave/src/arch/openrisc/include/asm/atomic.h:69: unknown
> opcode2 `l.swa'.Error: : => 71
> + /home/kisskb/slave/src/arch/openrisc/include/asm/atomic.h: Error:
> unknown opcode2 `l.lwa'.: 70, 69, 107 => 70, 79, 107, 69, 78
> + /home/kisskb/slave/src/arch/openrisc/include/asm/atomic.h: Error:
> unknown opcode2 `l.swa'.: 72, 111, 71 => 71, 111, 72, 80, 81
> + /home/kisskb/slave/src/arch/openrisc/include/asm/futex.h: Error:
> unknown opcode2 `l.lwa'.: => 54, 60, 63, 51, 108, 57
> + /home/kisskb/slave/src/arch/openrisc/include/asm/futex.h: Error:
> unknown opcode2 `l.swa'.: => 62, 112, 53, 59, 65, 56
>
> OpenRISC needs an updated toolchain.
Hi Geert,
Thansk for the report. I have updated the toolchain that is pointed to
by make.cross [1] a few weeks back. Fengguang and I updated the
make.cross tool which the build robot's point to a late tool chain [2],
what are you using?
If you can update to the or1k-linux-5.4.0-20170218 toolchain it should
fix these issues. Let me know if you have any questions.
Also, you may need a late version of QEMU if you are doing testing with
QEMU I had patched a few things there as well.
Also, there were a few more warnings pointed out by a make allmodconfig
test build. I have some patches I am about to send out for review with
fix those things up.
-Stafford
[1] https://lkml.org/lkml/2017/3/5/182
[2] https://github.com/openrisc/or1k-gcc/releases/download/or1k-5.4.0-20170218/or1k-linux-5.4.0-20170218.tar.xz
> > [1] http://kisskb.ellerman.id.au/kisskb/head/4495c08e84729385774601b5146d51d9e5849f81/ (all 266 configs)
> > [3] http://kisskb.ellerman.id.au/kisskb/head/c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201/ (all 266 configs)
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
> _______________________________________________
> OpenRISC mailing list
> OpenRISC@lists.librecores.org
> https://lists.librecores.org/listinfo/openrisc
next prev parent reply other threads:[~2017-03-13 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 8:43 Geert Uytterhoeven
2017-03-13 10:15 ` Geert Uytterhoeven
2017-03-13 14:12 ` Stafford Horne [this message]
2017-03-13 14:17 ` [OpenRISC] " Geert Uytterhoeven
2017-03-13 15:10 ` Stafford Horne
2017-03-14 11:36 ` Michael Ellerman
2017-03-14 12:54 ` Stafford Horne
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=20170313141228.GA2418@lianli.shorne-pla.net \
--to=shorne@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=openrisc@lists.librecores.org \
--cc=sfr@canb.auug.org.au \
/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®