[lkml]   [2015]   [Sep]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Adi-buildroot-devel] [Consult] blackfin: About one building break issue for STACKTRACE
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 . Upstream GCC5 isn't ported to Blackfin properly.

After a simply trying, I guess, this issue is not quite difficult to be

- 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.


> 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

 \ /
  Last update: 2015-09-05 02:01    [W:0.051 / U:0.152 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site