Richard Earnshaw <[email protected]> writes: > On 27/09/2022 16:24, Kyrylo Tkachov via Gcc-patches wrote: >> >>> -----Original Message----- >>> From: Andrea Corallo <[email protected]> >>> Sent: Tuesday, September 27, 2022 11:06 AM >>> To: Kyrylo Tkachov <[email protected]> >>> Cc: Andrea Corallo via Gcc-patches <[email protected]>; Richard >>> Earnshaw <[email protected]>; nd <[email protected]> >>> Subject: Re: [PATCH 9/15] arm: Set again stack pointer as CFA reg when >>> popping if necessary >>> >>> Kyrylo Tkachov <[email protected]> writes: >>> >>>> Hi Andrea, >>>> >>>>> -----Original Message----- >>>>> From: Gcc-patches <gcc-patches- >>>>> [email protected]> On Behalf Of Andrea >>>>> Corallo via Gcc-patches >>>>> Sent: Friday, August 12, 2022 4:34 PM >>>>> To: Andrea Corallo via Gcc-patches <[email protected]> >>>>> Cc: Richard Earnshaw <[email protected]>; nd <[email protected]> >>>>> Subject: [PATCH 9/15] arm: Set again stack pointer as CFA reg when >>> popping >>>>> if necessary >>>>> >>>>> Hi all, >>>>> >>>>> this patch enables 'arm_emit_multi_reg_pop' to set again the stack >>>>> pointer as CFA reg when popping if this is necessary. >>>>> >>>> >>>> From what I can tell from similar functions this is correct, but could you >>> elaborate on why this change is needed for my understanding please? >>>> Thanks, >>>> Kyrill >>> >>> Hi Kyrill, >>> >>> sure, if the frame pointer was set, than it is the current CFA register. >>> If we request to adjust the current CFA register offset indicating it >>> being SP (while it's actually FP) that is indeed not correct and the >>> incoherence we will be detected by an assertion in the dwarf emission >>> machinery. >> Thanks, the patch is ok >> Kyrill >> >>> >>> Best Regards >>> >>> Andrea > > Hmm, wait. Why would a multi-reg pop be updating the stack pointer?
Hi Richard, not sure I understand, isn't any pop updating SP by definition? BR Andrea
