From: Oleg Nesterov <oleg@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Mark Salter <msalter@redhat.com>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
uclinux-h8-devel@lists.sourceforge.jp,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"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: Tue, 25 Aug 2015 18:23:12 +0200 [thread overview]
Message-ID: <20150825162312.GA7098@redhat.com> (raw)
In-Reply-To: <20150825161145.GA29908@redhat.com>
On 08/25, Oleg Nesterov wrote:
>
> OK, this is gcc bug. But we probably need the workaround, and I don't
> have a h8300 machine so I can't test the fix.
>
> Could you please try to compile kernel/rcu/sync.o with the patch below?
> Just to know how "stable" this bug is. I expect the compilation should
> fail again, rcutiny.h:rcu_barrier() is "inline" too.
Wait, I reproduced the same problem on x86. Thanks.
Oleg.
next prev parent reply other threads:[~2015-08-25 16:25 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 [this message]
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=20150825162312.GA7098@redhat.com \
--to=oleg@redhat.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=msalter@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox