On Mon, Jul 4, 2016 at 8:58 PM, Prasad Ghangal wrote:
> On 4 July 2016 at 15:17, Richard Biener wrote:
>> On Sun, Jul 3, 2016 at 9:34 AM, Prasad Ghangal
>> wrote:
>>> In this patch, I am passing labels and vars with internal function and
>>> handling them in tree-cfg for parsing PHI.
>>> For fi
On 4 July 2016 at 15:17, Richard Biener wrote:
> On Sun, Jul 3, 2016 at 9:34 AM, Prasad Ghangal
> wrote:
>> In this patch, I am passing labels and vars with internal function and
>> handling them in tree-cfg for parsing PHI.
>> For first label, label_to_block() gives correct basic block and I am
On Sun, Jul 3, 2016 at 9:34 AM, Prasad Ghangal wrote:
> In this patch, I am passing labels and vars with internal function and
> handling them in tree-cfg for parsing PHI.
> For first label, label_to_block() gives correct basic block and I am
> getting proper edges but for other labels the functio
In this patch, I am passing labels and vars with internal function and
handling them in tree-cfg for parsing PHI.
For first label, label_to_block() gives correct basic block and I am
getting proper edges but for other labels the function is giving NULL.
test-case :
void __GIMPLE () foo()
{
int
On Fri, Jul 1, 2016 at 1:57 PM, Prasad Ghangal wrote:
> On 29 June 2016 at 12:42, Richard Biener wrote:
>> On Tue, Jun 28, 2016 at 4:16 PM, Prasad Ghangal
>> wrote:
>>> Hi,
>>>
>>> For handling PHI, it expects cfg to be built before. So I was
>>> wondering how are we going to handle this? Do we
On 29 June 2016 at 12:42, Richard Biener wrote:
> On Tue, Jun 28, 2016 at 4:16 PM, Prasad Ghangal
> wrote:
>> Hi,
>>
>> For handling PHI, it expects cfg to be built before. So I was
>> wondering how are we going to handle this? Do we need to build cfg
>> while parsing only?
>
> For handling PHIs
On Tue, Jun 28, 2016 at 4:16 PM, Prasad Ghangal
wrote:
> Hi,
>
> For handling PHI, it expects cfg to be built before. So I was
> wondering how are we going to handle this? Do we need to build cfg
> while parsing only?
For handling PHIs we need to have a CFG in the sense that the GIMPLE PHI
data s
Hi,
For handling PHI, it expects cfg to be built before. So I was
wondering how are we going to handle this? Do we need to build cfg
while parsing only?
Thanks,
Prasad
