From: Guenter Roeck <linux@roeck-us.net>
To: Yoshinori Sato <ysato@users.sourceforge.jp>
Cc: uclinux-h8-devel@lists.sourceforge.jp,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: h8300 build failures ijn linux-next
Date: Mon, 24 Aug 2015 11:34:20 -0700 [thread overview]
Message-ID: <55DB63AC.7070305@roeck-us.net> (raw)
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 ?
Thanks,
Guenter
next reply other threads:[~2015-08-24 18:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 18:34 Guenter Roeck [this message]
2015-08-25 5:56 ` h8300 build failures ijn linux-next 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
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=55DB63AC.7070305@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=uclinux-h8-devel@lists.sourceforge.jp \
--cc=ysato@users.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.