Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756718AbbGTVba (ORCPT ); Mon, 20 Jul 2015 17:31:30 -0400 Received: from blu004-omc1s16.hotmail.com ([65.55.116.27]:62254 "EHLO BLU004-OMC1S16.hotmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752290AbbGTVb2 (ORCPT ); Mon, 20 Jul 2015 17:31:28 -0400 X-TMN: [+ycRPNy9oe7T+evxXIv0eoKDJOSbnv3y] X-Originating-Email: [xili_gchen_5257@hotmail.com] Message-ID: Date: Tue, 21 Jul 2015 05:32:52 +0800 From: Chen Gang User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Hans-Peter Nilsson CC: jespern@axis.com, starvik@axis.com, linux-kernel@vger.kernel.org, linux-cris-kernel@axis.com Subject: Re: [Consult] cris: arch-v10: About $dtp0 register References: <201507071205.t67C5Ktk007837@ignucius.se.axis.com> In-Reply-To: Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 20 Jul 2015 21:31:26.0294 (UTC) FILETIME=[6EC5A760:01D0C333] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 4417 Lines: 104 On 7/9/15 08:44, Chen Gang wrote: > On 07/07/2015 08:05 PM, Hans-Peter Nilsson wrote: >> >> As a collateral, can I have an "upstream" GIT (slug and) commit >> id I can use to compile a CRIS v10 kernel, possibly modulo this >> issue? I need to use the kernel as a test-case for a gcc issue. >> I'll use Segher Boessenkool "buildall" kernelbuild scripts, but >> I'm missing a compilable kernel commit-id. (No, I haven't >> actually followed my own advice but by your email I'm guessing >> CRIS v10 isn't currently compilable.) >> 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 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:789, 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) ^ 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 0xbf0fb8 ccp_fold_stmt ../../gcc/gcc/tree-ssa-ccp.c:2215 0xc7f8da substitute_and_fold_dom_walker::before_dom_children(basic_block_def*) ../../gcc/gcc/tree-ssa-propagate.c:1226 0xe448f7 dom_walker::walk(basic_block_def*) ../../gcc/gcc/domwalk.c:177 0xc7f0d9 substitute_and_fold(tree_node* (*)(tree_node*), bool (*)(gimple_stmt_iterator*), bool) ../../gcc/gcc/tree-ssa-propagate.c:1319 0xbe967c ccp_finalize ../../gcc/gcc/tree-ssa-ccp.c:951 0xbe967c do_ssa_ccp ../../gcc/gcc/tree-ssa-ccp.c:2410 0xbe967c execute ../../gcc/gcc/tree-ssa-ccp.c:2442 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See for instructions. make[2]: *** [kernel/rcu/rcutorture.o] Error 1 make[1]: *** [kernel/rcu] Error 2 make: *** [kernel] Error 2 [root@localhost build-gcc-cris]# /upstream/release-cris/bin/cris-gchen-linux-gcc -v Using built-in specs. COLLECT_GCC=/upstream/release-cris/bin/cris-gchen-linux-gcc COLLECT_LTO_WRAPPER=/upstream/release-cris/libexec/gcc/cris-gchen-linux/6.0.0/lto-wrapper Target: cris-gchen-linux Configured with: ../gcc/configure --target=cris-gchen-linux --disable-nls --enable-languages=c --disable-threads --disable-shared --disable-libssp --disable-libquadmath --disable- libgomp --disable-libatomic --prefix=/upstream/release-cris --without-headers Thread model: single gcc version 6.0.0 20150720 (experimental) (GCC) If no any additional response, I shall try to fix it in the next month. Thanks. > > Excuse me, I am not quite understand your meaning, welcome additional > details explanations. > > And for me, hope the details below are useful for what you said above ( > but I am not quite sure). > > - I use the linux-next git tree which everyone can "git clone": > "git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git", > and I often use "git remote update" to get the latest release. > > - With the related patches I have sent, the "git tag" next-20150702 can > pass allmodconfig with the cross raw compiler (allmodconfig selects > CRIS v10). > > - Normally, I send patches to kernel mailing list with "Signed-of-by" > with my own mail address by "git commit -a -s". If the patch passes > review, it will be integrated into linux-next tree, then to master. > > Thanks. > -- Chen Gang Open, share, and attitude like air, water, and life which God blessed -- 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/