linux-kernel - Re: [Adi-buildroot-devel] [Consult] blackfin: About one building break issue for STACKTRACE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 05 Sep 2015 07:39:24 +0800
From:	Chen Gang <gchen_5i5j@...n.com>
To:	"Zhang, Sonic" <Sonic.Zhang@...log.com>,
	"realmz6@...il.com" <realmz6@...il.com>,
	Richard Weinberger <richard.weinberger@...il.com>
CC:	"adi-buildroot-devel@...ts.sourceforge.net" 
	<adi-buildroot-devel@...ts.sourceforge.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Bernd Schmidt <bernds@...esourcery.com>
Subject: Re: [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 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/