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][Binutils][AArch64/Arm] Update testcases fixing endiannes and linux targets


Hi Nick,

> 
> Hi Tamar,
> 
> > It turns out that the start address across baremetal and linux builds
> > isn't entirely predictable without a linker script.
> 
> Do you know about the --entry=<address> linker command line option ?
> 

Yes, I was using it but specifying a symbol and setting the text-segment start,
-e v1 -Ttext-segment=0x400000. I wasn't aware that -e could also take an address!

Though the problem is I want v1 at 0x400000, and I can't seem to be able to guarantee
that with just the cmdline flags. It seems to be putting v1 at 0x4000b0 when using -linux-gnue
and I couldn't see why it's adding the extra 0xb0.. 

Cheers,
Tamar

> 
> > Ok for master? and for backport to binutils-2.32?
> 
> Yes and yes.
> 
> > binutils/ChangeLog:
> > 2019-03-26  Tamar Christina  <tamar.christina@arm.com>
> >
> > 	* testsuite/binutils-all/aarch64/in-order-all.d: Update.
> > 	* testsuite/binutils-all/aarch64/in-order.d: Likewise.
> > 	* testsuite/binutils-all/aarch64/out-of-order-all.d: Likewise.
> > 	* testsuite/binutils-all/aarch64/out-of-order.d: Likewise.
> > 	* testsuite/binutils-all/aarch64/out-of-order.s: Likewise.
> > 	* testsuite/binutils-all/arm/in-order-all.d: Likewise.
> > 	* testsuite/binutils-all/arm/in-order.d: Likewise.
> > 	* testsuite/binutils-all/arm/out-of-order-all.d: Likewise.
> > 	* testsuite/binutils-all/arm/out-of-order.d: Likewise.
> > 	* testsuite/binutils-all/arm/out-of-order.s: Likewise.
> 
> Cheers
>   Nick
> 


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