This is the mail archive of the
mailing list for the binutils project.
Re: Tracing Android NDK's R_ARM_THM_CALL Truncate Problem
- From: lin zuojian <manjian2006 at gmail dot com>
- To: amodra at gmail dot com, will dot newton at linaro dot org
- Cc: "binutils at sourceware dot org" <binutils at sourceware dot org>
- Date: Fri, 28 Mar 2014 21:09:26 +0800
- Subject: Re: Tracing Android NDK's R_ARM_THM_CALL Truncate Problem
- Authentication-results: sourceware.org; auth=none
- References: <20140328094929 dot GA3768 at ubuntu> <CANu=Dmic6dcw+vxFL_y=EsuKkoGrDfKoje39bw6Pi4YJnAcXYg at mail dot gmail dot com> <20140328114853 dot GA2715 at lin-desktop> <20140328125952 dot GA4066 at lin-desktop>
I was completely misunderstood about this behavior.Here's what the
/* Default values. */
/* Thumb branch range is +-4MB has to be used as the default
maximum size (a given section can contain both ARM and Thumb
code, so the worst case has to be taken into account).
This value is 24K less than that, which allows for 2025
12-byte stubs. If we exceed that, then we will fail to link.
The user will have to relink with an explicit group size
So this is cause by too many stubs in the same group,and I have to
"relink with an explicit group size option".
But will the linker do the math for me? Retry with the suitable
parameter when fail for example.
On Fri, Mar 28, 2014 at 08:59:52PM +0800, lin zuojian wrote:
> I read the code again.And I think the structure is correct.I was
> wrong about the last message. Let's focus on the stub grouping size.
> linzu zuojian