On 07/28/2015 01:06 PM, Richard Biener wrote:
As Jakub said this is not the full story if you factor in type-based
aliasing. Also
you of course have to account for the offset in operand 1.
Okay. We understood the details after a bit of reading.
For statement involving MEM[...], TREE_TYPE (
On Mon, Jul 27, 2015 at 4:43 PM, Uday P. Khedker wrote:
>
>
> Jakub Jelinek wrote on Monday 27 July 2015 03:50 PM:
>>
>> On Mon, Jul 27, 2015 at 03:35:45PM +0530, Uday Khedker wrote:
>>>
>>> We are interested in extracting the type of a tree node that appears
>>> within
>>> MEM_REF.
>>>
>>> Given
Jakub Jelinek wrote on Monday 27 July 2015 03:50 PM:
On Mon, Jul 27, 2015 at 03:35:45PM +0530, Uday Khedker wrote:
We are interested in extracting the type of a tree node that appears within
MEM_REF.
Given a C program:
struct node * * pvar;
struct node qvar;
pvar = (struct nod
On Mon, Jul 27, 2015 at 12:20 PM, Jakub Jelinek wrote:
> On Mon, Jul 27, 2015 at 03:35:45PM +0530, Uday Khedker wrote:
>> We are interested in extracting the type of a tree node that appears within
>> MEM_REF.
>>
>> Given a C program:
>>
>> struct node * * pvar;
>> struct node qvar;
>>
On Mon, Jul 27, 2015 at 03:35:45PM +0530, Uday Khedker wrote:
> We are interested in extracting the type of a tree node that appears within
> MEM_REF.
>
> Given a C program:
>
> struct node * * pvar;
> struct node qvar;
> pvar = (struct node * *) malloc (sizeof (struct node *));
>
We are interested in extracting the type of a tree node that appears
within MEM_REF.
Given a C program:
struct node * * pvar;
struct node qvar;
pvar = (struct node * *) malloc (sizeof (struct node *));
*pvar = &qvar;
It is transformed into the following GIMPLE code:
void *
