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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 15 Sep 2014 17:49:49 +0200 From: Hans-Peter Nilsson <hans-peter.nilsson@...s.com> To: linux@...ck-us.net CC: jespern@...s.com, linux-cris-kernel@...s.com, linux-kernel@...r.kernel.org, grant.likely@...aro.org, edgar.iglesias@...il.com Subject: Re: Status of 'cris' architecture support in Linux kernel Following up on Jesper's reply... > From: Jesper Nilsson <jespern@...s.com> > Date: Mon, 15 Sep 2014 16:52:03 +0200 > > Toolchain > > > > Creating a toolchain from upstream sources required a number of patches. > > - gcc 4.7.4 > > Requires a backport from upstream gcc to compile. > > Later versions of gcc (4.8.3, 4.9.1) fail with internal compiler errors > > even after patching. This sounds like PR61737 (fixed; use 4.9.2 not released yet), but of course with the above sentence serving as your complete bug-report (or did I miss one?) that will only be a guess. > I'm using gcc 4.7.2, but of course, that is a locally built > version that might have patches not upstream > (although I doubt it knowing the gcc CRIS maintainer :-) (oops. *blush*) The TLS stuff is unfortunately not upstreamed at this time. Unimportant when building the kernel, but mentioned for completeness. (The bad excuse is that I originally awaited pre-v32 kernels to get the corresponding TLS support so I wouldn't have to do ugly pre-vs.-v32 conditionals, then the whole thing lost priority, and now I avoid adding code I can't/won't test - the glibc end isn't upstreamed either. Sorry.) brgds, H-P -- 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