This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [Patch mach-o] correct vmsize calculation for zerofill cases.

From: Iain Sandoe <developer at sandoe-acoustics dot co dot uk>
To: Tristan Gingold <gingold at adacore dot com>
Cc: binutils Development <binutils at sourceware dot org>
Date: Fri, 10 Feb 2012 11:43:27 +0000
Subject: Re: [Patch mach-o] correct vmsize calculation for zerofill cases.
References: <D8534ABF-9151-4221-B88F-72577F3A978E@sandoe-acoustics.co.uk> <F60E381C-0D27-41C2-9C8D-5E2E92179C6C@adacore.com>

On 9 Feb 2012, at 15:06, Tristan Gingold wrote:

OK?
Ok, although I have a suggestion below in the patch.

done & applied.

[ Maybe we should have a linked list of section per segment ]

once we start to do read/write/update and other filetypes, it would seem that something like that would be useful/required. - for MH_OBJECTs only there's not much we can change -- unless.... .. we could see if ordering the sections from GAS actually causes any onward tool-chain problems... but maybe leave until we have a basic system working?

Iain

References:
- [Patch mach-o] correct vmsize calculation for zerofill cases.
  - From: Iain Sandoe
- Re: [Patch mach-o] correct vmsize calculation for zerofill cases.
  - From: Tristan Gingold

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]