lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170313141228.GA2418@lianli.shorne-pla.net>
Date:   Mon, 13 Mar 2017 23:12:28 +0900
From:   Stafford Horne <shorne@...il.com>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        openrisc@...ts.librecores.org,
        Michael Ellerman <mpe@...erman.id.au>
Subject: Re: [OpenRISC] Build regressions/improvements in v4.11-rc2

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@...ux-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@...ux-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@...ts.librecores.org
> https://lists.librecores.org/listinfo/openrisc

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ