linux-kernel - Re: h8300 build failures ijn linux-next

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]

Date:	Tue, 25 Aug 2015 10:27:55 -0400
From:	Mark Salter <msalter@...hat.com>
To:	Yoshinori Sato <ysato@...rs.sourceforge.jp>,
	Guenter Roeck <linux@...ck-us.net>
Cc:	uclinux-h8-devel@...ts.sourceforge.jp,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: h8300 build failures ijn linux-next

On Tue, 2015-08-25 at 14:56 +0900, Yoshinori Sato wrote:
> On Tue, 25 Aug 2015 03:34:20 +0900,
> Guenter Roeck wrote:
> > 
> > Hi,
> > 
> > In linux-next as of today (0824), all h8300 builds fail for me with an 
> > internal
> > compiler error.
> > 
> > Building h8300:allnoconfig ... failed
> > --------------
> > Error log:
> > 
> > In file included from include/linux/rcupdate.h:429:0,
> >                  from include/linux/rcusync.h:5,
> >                  from kernel/rcu/sync.c:1:
> > include/linux/rcutiny.h: In function ‘rcu_barrier_sched’:
> > include/linux/rcutiny.h:55:20: internal compiler error: Segmentation 
> > fault
> >  static inline void rcu_barrier_sched(void)
> >                     ^
> > 
> > I tried both gcc 5.1 and 5.2, built with the patch set available to me.
> > 
> > Is there a more recent compiler / patch set available that might fix 
> > the problem ?
> > 
> 
> No.
> I tried gcc 6.0. It got same error.
> It looks optimization problem on h8300 target.
> I will investigate it.

I get the same ICE with c6x gcc 5.1

> > Thanks,
> > Guenter
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/