All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Jim Davis <jim.epost@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: arch linux with gcc 5.1.0 doesn't like include/linux/rcutiny.h
Date: Mon, 15 Jun 2015 17:27:49 -0700	[thread overview]
Message-ID: <20150616002748.GA28766@x> (raw)
In-Reply-To: <20150616002031.GD3913@linux.vnet.ibm.com>

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

      reply	other threads:[~2015-06-16  0:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16  0:11 arch linux with gcc 5.1.0 doesn't like include/linux/rcutiny.h Jim Davis
2015-06-16  0:20 ` Paul E. McKenney
2015-06-16  0:27   ` Josh Triplett [this message]

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=20150616002748.GA28766@x \
    --to=josh@joshtriplett.org \
    --cc=jim.epost@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    /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.