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: Large lma delta using binutils 2.19

From: "James Blackburn" <james dot blackburn at broadcom dot com>
To: "H.J. Lu" <hjl dot tools at gmail dot com>
Cc: "binutils at sourceware dot org" <binutils at sourceware dot org>
Date: Tue, 2 Mar 2010 17:24:55 +0000
Subject: Re: Large lma delta using binutils 2.19
References: <4B8D4174.3020103@broadcom.com> <6dc9ffc81003020914o23359accw8b88640f603fa80c@mail.gmail.com>

Thanks for the prompt reply!

On 02/03/2010 17:14, H.J. Lu wrote:

to ensure that LMA of .data.init_task section is always equal to its
VMA...  You can add AT (ADDR(section)) to force LMA of
.data.init_task section equal to its VMA. It will work with both old
and new linkers.

I spotted the commit that made the change. Unfortunately we have a whole bunch of existing chip test suites, orthogonal to the tool-chain, that use their own custom linker scripts. It would be unfortunate to invalidate all these existing tests...

Isn't this a general issue for memory constrainedembedded targets?

Cheers,
James

Follow-Ups:
- Re: Large lma delta using binutils 2.19
  - From: Alan Modra

References:
- Large lma delta using binutils 2.19
  - From: James Blackburn
- Re: Large lma delta using binutils 2.19
  - From: H.J. Lu

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