Re: [GCC16,RFC,V2 04/14] aarch64: add new definition for post-index st2g

2025-05-01 Thread Richard Sandiford
Indu Bhagat writes: > On 4/15/25 11:52 AM, Richard Sandiford wrote: >> Indu Bhagat writes: >>> Using post-index st2g is a faster way of memory tagging/untagging. >>> Because a post-index 'st2g tag, [addr], #32' is equivalent to: >>> stg tag, addr, #0 >>> stg tag, addr, #16 >>> add add

Re: [GCC16,RFC,V2 04/14] aarch64: add new definition for post-index st2g

2025-04-22 Thread Indu Bhagat
On 4/15/25 11:52 AM, Richard Sandiford wrote: Indu Bhagat writes: Using post-index st2g is a faster way of memory tagging/untagging. Because a post-index 'st2g tag, [addr], #32' is equivalent to: stg tag, addr, #0 stg tag, addr, #16 add addr, addr, #32 TBD: - Currently generated

Re: [GCC16,RFC,V2 04/14] aarch64: add new definition for post-index st2g

2025-04-15 Thread Richard Sandiford
Indu Bhagat writes: > Using post-index st2g is a faster way of memory tagging/untagging. > Because a post-index 'st2g tag, [addr], #32' is equivalent to: >stg tag, addr, #0 >stg tag, addr, #16 >add addr, addr, #32 > > TBD: > - Currently generated by in the aarch64 backend. Not sure

[GCC16,RFC,V2 04/14] aarch64: add new definition for post-index st2g

2025-04-11 Thread Indu Bhagat
Using post-index st2g is a faster way of memory tagging/untagging. Because a post-index 'st2g tag, [addr], #32' is equivalent to: stg tag, addr, #0 stg tag, addr, #16 add addr, addr, #32 TBD: - Currently generated by in the aarch64 backend. Not sure if this is the right way to do i