linux-kernel - Re: Microblaze toolchain

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 12 May 2008 08:43:08 +1000
From:	John Williams <john.williams@...alogix.com>
To:	monstr@...nam.cz
Cc:	Stephen Neuendorffer <stephen.neuendorffer@...inx.com>,
	John Linn <John.Linn@...inx.com>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	Arnd Bergmann <arnd@...db.de>,
	microblaze-uclinux@...e.uq.edu.au,
	Grant Likely <grant.likely@...retlab.ca>
Subject: Re: Microblaze toolchain - libc

Hi Michal,

On Sun, 2008-05-11 at 16:05 +0200, Michal Simek wrote:

> is it any movement in libc?
> I would like clear code around syscalls.

I can't see anything radical happening with glibc / uClibc in the short
term.  My suggestion is you make sure the kernel builds with current
toolchain.  

I'm not personally concerned about minor bloat of adding syscalls like
openat() that are not currently used - 1 or 2 K for extra entries in
syscall table, and a few hundred bytes per sys_wrapper really is not on
the radar if glibc is considered a sensible library for Microblaze +
MMU!

Regards,

John

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