From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934287AbbIDXhq (ORCPT ); Fri, 4 Sep 2015 19:37:46 -0400 Received: from smtpfree.forptr.21cn.com ([183.56.131.159]:42657 "EHLO 21cn.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S934120AbbIDXhb (ORCPT ); Fri, 4 Sep 2015 19:37:31 -0400 HMM_SOURCE_IP: 10.64.8.32:62048.752332305 HMM_ATTACHE_NUM: 0000 HMM_SOURCE_TYPE: SMTP 0/X-Total-Score: 0: 1/X-Total-Score: 0: X-FILTER-SCORE: to=<8386938f85946184908586949096938486939a4f84908e>, score=<1441409847ggggggghhhggggggggggggX34/nzeuvWWWWWXWW3WW4W> X-REAL-FROM: gchen_5i5j@21cn.com X-Receive-IP: 124.166.242.182 Message-ID: <55EA2BAC.9070907@21cn.com> Date: Sat, 05 Sep 2015 07:39:24 +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: "Zhang, Sonic" , "realmz6@gmail.com" , Richard Weinberger CC: "adi-buildroot-devel@lists.sourceforge.net" , "linux-kernel@vger.kernel.org" , Bernd Schmidt Subject: Re: [Adi-buildroot-devel] [Consult] blackfin: About one building break issue for STACKTRACE References: <55311283.1050404@hotmail.com> <55E7B906.9050907@21cn.com> In-Reply-To: <55E7B906.9050907@21cn.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 9/3/15 11:05, Chen Gang wrote: > On 4/17/15 22:02, Chen Gang wrote: >> On 4/17/15 11:02, Zhang, Sonic wrote: >>> Hi Gang, >>> >>> Please only use the GCC for Blackfin 2013R1 or 2014R1 from https://sourceforge.net/projects/adi-buildroot/files/ . Upstream GCC5 isn't ported to Blackfin properly. >>> After a simply trying, I guess, this issue is not quite difficult to be fixed. - The current gcc 'think', our current usage is incorrect. - But the original gcc 'think', our current usage is OK. - The related commits is "e52beba PR debug/54694" in gcc git repo. I shall try to consult the gcc related members for it, so we can make sure whether we need fix our code or the new gcc need be fixed. Thanks. > > I shall try to merge the 2014R1 to the latest gcc upstream to support > the related feature in my free time. > > I hope I can finish within 2 months (although I am not quite sure -- > maybe need 3 months or more). > > Welcome any related ideas, suggestions and completions. > > Thanks. > >> >> OK, thank you very much for your reply. :-) >> >> >> For me, I want to let gcc5 support Blackfin properly, but sorry, at >> present I can not. >> >> - In honest, I am still not quite familiar with gcc (although I am >> trying and improving). >> >> - This year, I have no enough time resource for it (I am mainly for >> upstream qemu this year). >> >> But if next year, upstream gcc is still not ported to Blackfin properly, >> I shall try. >> >> However, there are still several another issues for upstream blackfin >> gcc5 (they are all coredumps), I should still try to analyze them and >> find root causes, hope I can finish within this month. >> >> >> Thanks. >> > -- Chen Gang (陈刚) Open, share, and attitude like air, water, and life which God blessed