From: Chen Gang <gchen_5i5j@21cn.com>
To: "Zhang, Sonic" <Sonic.Zhang@analog.com>,
"realmz6@gmail.com" <realmz6@gmail.com>,
Richard Weinberger <richard.weinberger@gmail.com>
Cc: "adi-buildroot-devel@lists.sourceforge.net"
<adi-buildroot-devel@lists.sourceforge.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Bernd Schmidt <bernds@codesourcery.com>
Subject: Re: [Adi-buildroot-devel] [Consult] blackfin: About one building break issue for STACKTRACE
Date: Sat, 05 Sep 2015 07:39:24 +0800 [thread overview]
Message-ID: <55EA2BAC.9070907@21cn.com> (raw)
In-Reply-To: <55E7B906.9050907@21cn.com>
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
prev parent reply other threads:[~2015-09-04 23:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 15:21 [Consult] blackfin: About one building break issue for STACKTRACE Chen Gang
2015-04-17 3:02 ` [Adi-buildroot-devel] " Zhang, Sonic
2015-04-17 14:02 ` Chen Gang
2015-04-17 22:20 ` Chen Gang
2015-04-19 4:58 ` Chen Gang
[not found] ` <55311283.1050404@hotmail.com>
2015-09-03 3:05 ` Chen Gang
2015-09-04 23:39 ` Chen Gang [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=55EA2BAC.9070907@21cn.com \
--to=gchen_5i5j@21cn.com \
--cc=Sonic.Zhang@analog.com \
--cc=adi-buildroot-devel@lists.sourceforge.net \
--cc=bernds@codesourcery.com \
--cc=linux-kernel@vger.kernel.org \
--cc=realmz6@gmail.com \
--cc=richard.weinberger@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox