From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Mark Salter <msalter@redhat.com>,
uclinux-h8-devel@lists.sourceforge.jp,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Oleg Nesterov <oleg@redhat.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Josh Triplett <josh@joshtriplett.org>
Subject: Re: h8300 build failures in linux-next (in rcu code, gcc 5.x related, not limited to h8300)
Date: Wed, 26 Aug 2015 01:51:52 +0900 [thread overview]
Message-ID: <871terjopj.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <55DC83C7.1060809@roeck-us.net>
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@users.sourceforge.jp>
next prev parent reply other threads:[~2015-08-25 16:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 18:34 h8300 build failures ijn linux-next Guenter Roeck
2015-08-25 5:56 ` Yoshinori Sato
2015-08-25 14:27 ` Mark Salter
2015-08-25 15:03 ` h8300 build failures in linux-next (in rcu code, gcc 5.x related, not limited to h8300) Guenter Roeck
2015-08-25 16:11 ` Oleg Nesterov
2015-08-25 16:23 ` Oleg Nesterov
2015-08-25 16:51 ` Yoshinori Sato [this message]
2015-08-25 17:34 ` Oleg Nesterov
2015-08-25 18:02 ` Oleg Nesterov
2015-08-25 18:16 ` Mark Salter
2015-08-25 18:45 ` [PATCH] rcu: change _wait_rcu_gp() to work around gcc 67055 bug Oleg Nesterov
2015-08-25 19:00 ` Paul E. McKenney
2015-08-25 19:02 ` Oleg Nesterov
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=871terjopj.wl-ysato@users.sourceforge.jp \
--to=ysato@users.sourceforge.jp \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=msalter@redhat.com \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=uclinux-h8-devel@lists.sourceforge.jp \
/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