Re: h8300 build failures in linux-next (in rcu code, gcc 5.x related, not limited to h8300)

[Yoshinori Sato]

On Wed, 26 Aug 2015 00:03:35 +0900,
Guenter Roeck wrote:
> 
> Hi Mark,
> 
> On 08/25/2015 07:27 AM, Mark Salter wrote:
> > 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
> > 
> 
> Interesting. h8300 was the only gcc 5+ compiler I had used so far.
> Just for fun, I built an alpha toolchain with gcc 5.1. Same problem there.
> So it looks like it isn't a h8300 problem after all, it is a gcc problem.
> 
> Updated subject line, and copied rcu maintainers.
> 
> Guenter
> 

Yes.
gcc bug #67055.
Already fixed in trunk.

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