| 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
| ||
|
Date: Fri, 17 Apr 2015 22:02:43 +0800 From: Chen Gang <xili_gchen_5257@...mail.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> Subject: Re: [Adi-buildroot-devel] [Consult] blackfin: About one building break issue for STACKTRACE 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. > 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/
Powered by blists - more mailing lists