ping
From: Wilco Dijkstra
Sent: 12 September 2016 15:50
To: Richard Earnshaw; GCC Patches
Cc: nd
Subject: Re: [PATCH v2][AArch64] Fix symbol offset limit
Wilco wrote:
> The original example is from GCC itself, the fixed_regs array is small but
> due to
> optimization we c
ping
From: Wilco Dijkstra
Sent: 12 September 2016 15:50
To: Richard Earnshaw; GCC Patches
Cc: nd
Subject: Re: [PATCH v2][AArch64] Fix symbol offset limit
Wilco wrote:
> The original example is from GCC itself, the fixed_regs array is small but
> due to
> optimization we c
ping
From: Wilco Dijkstra
Sent: 12 September 2016 15:50
To: Richard Earnshaw; GCC Patches
Cc: nd
Subject: Re: [PATCH v2][AArch64] Fix symbol offset limit
Wilco wrote:
> The original example is from GCC itself, the fixed_regs array is small but
> due to
> optimization w
ping
From: Wilco Dijkstra
Sent: 12 September 2016 15:50
To: Richard Earnshaw; GCC Patches
Cc: nd
Subject: Re: [PATCH v2][AArch64] Fix symbol offset limit
Wilco wrote:
> The original example is from GCC itself, the fixed_regs array is small but
> due to
> optimization we c
ping
From: Wilco Dijkstra
Sent: 12 September 2016 15:50
To: Richard Earnshaw; GCC Patches
Cc: nd
Subject: Re: [PATCH v2][AArch64] Fix symbol offset limit
Wilco wrote:
> The original example is from GCC itself, the fixed_regs array is small but
> due to
> optimization we c
ping
Wilco wrote:
> The original example is from GCC itself, the fixed_regs array is small but
> due to
> optimization we can end up with &fixed_regs + 0x.
We could also check the bounds of each symbol if they exist, like the patch
below.
In aarch64_classify_symbol symbols a
Wilco wrote:
> The original example is from GCC itself, the fixed_regs array is small but
> due to
> optimization we can end up with &fixed_regs + 0x.
We could also check the bounds of each symbol if they exist, like the patch
below.
In aarch64_classify_symbol symbols are allowed f