This is the mail archive of the
mailing list for the binutils project.
Re: PATCH: Automatically apply an address offset when linking between XGATE and M68HC1x cores.
- From: Sean Keys <skeys at ipdatasys dot com>
- To: James Murray <jsm at jsm-net dot demon dot co dot uk>
- Cc: binutils at sourceware dot org
- Date: Sun, 15 Jul 2012 13:36:40 -0700
- Subject: Re: PATCH: Automatically apply an address offset when linking between XGATE and M68HC1x cores.
- References: <500237C1.firstname.lastname@example.org> <1342382653.27950.43.camel@jsm2>
It's basically the same concept. Although, if I recall correctly your
code only applies an offset, when linking M68HC1X symbols against XGATE
relocations. XGATE code generated using the M68HC1x assembler won't be
affected, including the "--xgate-ramoffset" option. The test suite
yields the same results with this patch applied.
It only applies when you use the XGATE tools. The --xgate-ramoffset
On 07/15/2012 01:04 PM, James Murray wrote:
On Sat, 2012-07-14 at 20:23 -0700, Sean Keys wrote:
Users of XGATE and M68HC1x Binutils have requested that the linker apply
an appropriate offset for one another, when linking between the two
cores. This offset is only applied when the address is within "shared
RAM". If the address falls outside this area, no offset is applied and
a warning is emitted.
How does this compare, interact (or conflict?) with the existing
(I won't have time to check the source for a few days.)