From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/4752 Path: news.gmane.org!not-for-mail From: Szabolcs Nagy Newsgroups: gmane.linux.lib.musl.general Subject: Re: Any plans on MMU-less support? Date: Sun, 30 Mar 2014 17:01:39 +0200 Message-ID: <20140330150139.GJ27448@port70.net> References: <5337BE64.2010504@gmail.com> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1396191717 13039 80.91.229.3 (30 Mar 2014 15:01:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 30 Mar 2014 15:01:57 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-4756-gllmg-musl=m.gmane.org@lists.openwall.com Sun Mar 30 17:01:53 2014 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1WUHFA-0003aG-VM for gllmg-musl@plane.gmane.org; Sun, 30 Mar 2014 17:01:53 +0200 Original-Received: (qmail 23911 invoked by uid 550); 30 Mar 2014 15:01:51 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 23903 invoked from network); 30 Mar 2014 15:01:51 -0000 Content-Disposition: inline In-Reply-To: <5337BE64.2010504@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:4752 Archived-At: * Smirnov Vladimir [2014-03-30 15:49:08 +0900]: > I wonder if MUSL have such roadmap or there is any hackish way to > add that support (may be some unoffitial patches). > My problem that i've stucked with old gcc toolchain and uClibc > supporting one widely used ARMv4 MMUless chip. looking at uClibc the main differences in a no-mmu system: fork is not available so related functions have to be changed/disabled (vfork, daemon, wordexp, forkpty, pthread_atfork) brk is not available so malloc needs to change mmap may need MAP_UNINITIALIZED flag for performance (and MAP_FIXED flag will fail) memory management related things may need to be changed/disabled (mprotect?,mlock,msync,..) for dynamic linking ldso and libc startup code may need some change (some targets (not arm) need fdpic or dsbt elf support) (others can use a shared flat binary format) pthread may need smaller default stack and more careful stack usage arm startup code needs a change according to http://git.uclibc.org/uClibc/tree/libc/sysdeps/linux/arm/crt1.S#n179 and you may need to fix various toolchain issues..