[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150616002748.GA28766@x>
Date: Mon, 15 Jun 2015 17:27:49 -0700
From: Josh Triplett <josh@...htriplett.org>
To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc: Jim Davis <jim.epost@...il.com>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: arch linux with gcc 5.1.0 doesn't like include/linux/rcutiny.h
On Mon, Jun 15, 2015 at 05:20:31PM -0700, Paul E. McKenney wrote:
> On Mon, Jun 15, 2015 at 05:11:16PM -0700, Jim Davis wrote:
> > Just an FYI, but with next-20150615 (and I think some previous days too IIRC),
> >
> > In file included from include/linux/rcupdate.h:429:0,
> > from include/linux/srcu.h:33,
> > from include/linux/notifier.h:15,
> > from include/linux/memory_hotplug.h:6,
> > from include/linux/mmzone.h:797,
> > from include/linux/gfp.h:5,
> > from include/linux/kmod.h:22,
> > from include/linux/module.h:13,
> > from kernel/rcu/rcutorture.c:28:
> > 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)
> > ^
> >
> > That's with a random configuration file setting
>
> I presume that you are reporting it to the gcc guys as well? If nothing
> else, for the obtuseness of the error message?
Agreed. Can you reproduce this with a preprocessed file ("make
kernel/rcu/rcutorture.i" first), and then provide that file in a bug
report to GCC?
- Josh Triplett
--
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