Hello,

Gentle ping for 

  https://gcc.gnu.org/ml/gcc-patches/2019-12/msg01398.html

I realize and certainly understand that this is
of lower importance than other matters currently being discussed
on the lists.

It's just that the end of stage 3 is imminent and I thought
we'd better at least agree on a way forward before it closes.

This particular change is an extraction of an hopefully
non controversial part of a more general change discussed
earlier. No ABI concern here.

Thanks in advance!

Cheers,

Olivier

> On 19 Dec 2019, at 18:38, Olivier Hainque <hain...@adacore.com> wrote:
> 
> Hello,
> 
> The attached patch is a standalone part of a slightly more
> general change last discussed here:
> 
>  https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02626.html
> 
> Which I re-tested successfully on aarch64-linux (bootstrap
> and regression test with --enable-languages=all + local tests
> with Ada stack-checking on a gcc-9 based toolchain in-house).
> 
> The change moves the definitions of PROBE_STACK_FIRST_REG
> and PROBE_STACK_SECOND_REG to a more appropriate place for such
> items (here, in aarch64.md as suggested by Richard), and adjust
> their value from r9/r10 to r10/r11 to free r9 for a possibly
> more general purpose (e.g. as a static chain at least on targets
> which have a private use of r18, such as Windows or Vxworks).
> 
> Is this ok to commit ?
> 
> Thanks in advance!
> 
> With Kind Regards,
> 
> Olivier
> 
> --
> 
>> 2019-11-07  Olivier Hainque  <hain...@adacore.com>
>> 
>>      * config/aarch64/aarch64.md: Define PROBE_STACK_FIRST_REGNUM
>>      and PROBE_STACK_SECOND_REGNUM constants, designating r10/r11.
>>      Replacements for the PROBE_STACK_FIRST/SECOND_REG constants in
>>      aarch64.c.
>>      * config/aarch64/aarch64.c (PROBE_STACK_FIRST_REG): Remove.
>>      (PROBE_STACK_SECOND_REG): Remove.
>>      (aarch64_emit_probe_stack_range): Adjust to the _REG -> _REGNUM
>>      suffix update for PROBE_STACK register numbers.
> 
> <0001-Move-and-adjust-PROBE_STACK-reg-definitions-for-aarc.patch.txt>

Reply via email to