From mint-bounce@lists.fishpool.fi Mon Jan 28 17:40:24 2008 Date: Mon, 28 Jan 2008 23:36:27 +0100 (CET) From: Frank Naumann X-X-Sender: fnaumann@localhost.localdomain To: mint Subject: Re: [MiNT] Alignment 2 In-Reply-To: <479E54DF.5050804@freesbee.fr> Message-ID: References: <4798E197.6050500@freesbee.fr> <479E54DF.5050804@freesbee.fr> User-Agent: Alpine 1.00 (LFD 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=- tagged_above=-50.5 required=7.0 WHITELISTED X-Spam-Level: X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: fnaumann@boerde.de Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Hello! > Question 2: Does Pexec load the executables at an address multiple of 4 ? In > other words, is the .text segment long aligned in memory ? Hehe, what do you think how the kernel manage the memory ... It don't waste it's time to manage 50 byte blocks, that's application area (e.g. MiNTLib malloc()/free()). The kernel manage big memory chunks, e.g. the smallest block you get from kernel by Mxalloc() is the system page size (8 kb [except 68000 CPU where it is 512 byte]). I don't looked at the code but I would assume that the Pexec loader load the code aligned into the memory block (the memory block is page aligned for sure). Regards, Frank -- ATARI FALCON 060 // MILAN 060 -------------------------------- http://sparemint.atariforge.org/ e-Mail: fnaumann@freemint.de