Snapshot gcc-5-20150308 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/5-20150308/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision
On 03/08/15 12:13, Richard Biener wrote:
I see. This basically creates two loop latches and thus will make our loop
detection code turn the loop into a fake loop nest. Not sure if that is a good
idea.
I'd have to sit down and ponder this for a while -- what would be the
register pressure im
On March 8, 2015 4:58:49 PM CET, Ajit Kumar Agarwal
wrote:
>
>
>-Original Message-
>From: Richard Biener [mailto:richard.guent...@gmail.com]
>Sent: Sunday, March 08, 2015 9:05 PM
>To: Ajit Kumar Agarwal; vmaka...@redhat.com; Jeff Law; gcc@gcc.gnu.org
>Cc: Vinod Kathail; Shail Aditya Gupt
On 03/08/15 09:35, Richard Biener wrote:
On March 8, 2015 3:39:08 PM CET, Ajit Kumar Agarwal
wrote:
Hello All:
The path splitting that replicates the code for better Data flow
Analysis available. One of the properties
of path splitting removes the joining nodes for the forked path like
IF-THE
-Original Message-
From: Richard Biener [mailto:richard.guent...@gmail.com]
Sent: Sunday, March 08, 2015 9:05 PM
To: Ajit Kumar Agarwal; vmaka...@redhat.com; Jeff Law; gcc@gcc.gnu.org
Cc: Vinod Kathail; Shail Aditya Gupta; Vidhumouli Hunsigida; Nagaraju Mekala
Subject: Re: Proposal for p
On March 8, 2015 3:39:08 PM CET, Ajit Kumar Agarwal
wrote:
>Hello All:
>
>The path splitting that replicates the code for better Data flow
>Analysis available. One of the properties
>of path splitting removes the joining nodes for the forked path like
>IF-THEN-ELSE and the Loops.
>
>The removal
Hello All:
The path splitting that replicates the code for better Data flow Analysis
available. One of the properties
of path splitting removes the joining nodes for the forked path like
IF-THEN-ELSE and the Loops.
The removal of joining nodes makes the path splitted into two independent
path
