Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751222AbbHEEc6 (ORCPT ); Wed, 5 Aug 2015 00:32:58 -0400 Received: from bes.se.axis.com ([195.60.68.10]:53143 "EHLO bes.se.axis.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750785AbbHEEc5 (ORCPT ); Wed, 5 Aug 2015 00:32:57 -0400 Date: Wed, 5 Aug 2015 06:32:54 +0200 Message-Id: <201508050432.t754Wstb005185@ignucius.se.axis.com> From: Hans-Peter Nilsson To: xili_gchen_5257@hotmail.com CC: jespern@axis.com, starvik@axis.com, linux-kernel@vger.kernel.org, linux-cris-kernel@axis.com In-reply-to: (message from Chen Gang on Mon, 20 Jul 2015 23:32:52 +0200) Subject: Re: [Consult] cris: arch-v10: About $dtp0 register MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 7BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1301 Lines: 33 > From: Chen Gang > Date: Mon, 20 Jul 2015 23:32:52 +0200 > On 7/9/15 08:44, Chen Gang wrote: > The latest upstream cris gcc will cause issue for next-20150720 with > allmodconfig (although it can let next-20150702 pass allmodconfig): > > CC [M] kernel/rcu/rcutorture.o [...] > include/linux/rcutiny.h:55:20: internal compiler error: Segmentation fault > static inline void rcu_barrier_sched(void) > ^ > 0xad879f crash_signal > ../../gcc/gcc/toplev.c:352 > 0xbf0fb8 tree_check(tree_node*, char const*, int, char const*, tree_code) > ../../gcc/gcc/tree.h:2857 > 0xbf0fb8 fold_builtin_alloca_with_align > ../../gcc/gcc/tree-ssa-ccp.c:2110 [...] > If no any additional response, I shall try to fix it in the next month. No need to enter a new bug report, this appears to be . It is also observed for other ports, at least with the original C++ test-case there. I added a reduced rcutorture.c to the bug-report. Thanks. brgds, H-P -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/