[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150825162312.GA7098@redhat.com>
Date: Tue, 25 Aug 2015 18:23:12 +0200
From: Oleg Nesterov <oleg@...hat.com>
To: Guenter Roeck <linux@...ck-us.net>
Cc: Mark Salter <msalter@...hat.com>,
Yoshinori Sato <ysato@...rs.sourceforge.jp>,
uclinux-h8-devel@...ts.sourceforge.jp,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Josh Triplett <josh@...htriplett.org>
Subject: Re: h8300 build failures in linux-next (in rcu code, gcc 5.x
related, not limited to h8300)
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.
--
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/
Powered by blists - more mailing lists