Re: Question on updating function body on specialized functions

2022-03-09 Thread Richard Biener via Gcc
On Tue, Mar 8, 2022 at 4:31 PM Erick Ochoa via Gcc wrote: > > Hi Martin! > > Thanks for replying, turns out that while I was trying to reply to you I > was able to get the answer. Turns out there is indeed one tree node which > is shared across the two functions. And that is > > TREE_OPERAND (MEM_

Re: Question on updating function body on specialized functions

2022-03-08 Thread Gary Oblock via Gcc
Erick my friend, That's exactly why I'm such a big fan of creating things anew each time I mess with them. 😉 Later, Gary From: Erick Ochoa Sent: Tuesday, March 8, 2022 7:29 AM To: Martin Jambor Cc: gcc@gcc.gnu.org Subject: Re: Question on updatin

Re: Question on updating function body on specialized functions

2022-03-08 Thread Erick Ochoa via Gcc
Hi Martin! Thanks for replying, turns out that while I was trying to reply to you I was able to get the answer. Turns out there is indeed one tree node which is shared across the two functions. And that is TREE_OPERAND (MEM_REF, 1). When I was assigning to TREE_TYPE ( TREE_OPERAND (MEM_REF, 1)

Re: Question on updating function body on specialized functions

2022-03-08 Thread Martin Jambor
Hi Erik, On Tue, Mar 08 2022, Erick Ochoa via Gcc wrote: > Hi, > > I have one function (F) that has been specialized for two different calling > contexts (F1 and F2) and two late SIMPLE_IPA_PASSes (A and B). Pass A > changes some MEM_REFs such that the type of MEM_REF is compatible with the > type

Question on updating function body on specialized functions

2022-03-08 Thread Erick Ochoa via Gcc
Hi, I have one function (F) that has been specialized for two different calling contexts (F1 and F2) and two late SIMPLE_IPA_PASSes (A and B). Pass A changes some MEM_REFs such that the type of MEM_REF is compatible with the type of the first operand of the expression. Pass A changes both F1 and F