On 2019-06-07 10:36 p.m., nick wrote:
> Greetings,
>
> In both the manual and general other places it seems that the old
> walk_dominator_tree is used instead
> of the current walk name. Trevor has been CCed as this change occurred it
> seems in 2013 but some of
> the callers including the m
Greetings,
In both the manual and general other places it seems that the old
walk_dominator_tree is used instead
of the current walk name. Trevor has been CCed as this change occurred it seems
in 2013 but some of
the callers including the manual are still out of date.
Sending patches for fixi
Snapshot gcc-8-20190607 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/8-20190607/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 8 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-8
On 6/7/19 8:25 AM, Richard Biener wrote:
On Wed, Jun 5, 2019 at 10:56 PM Andrew MacLeod wrote:
After the various discussions, I've evaluated how I think everything can
fit together, so this is my proposal for integration with trunk.
The complete Ranger prototype consists of 5 major component
Short summary:
a) we'll unify value_range and the irange API, confirm there are no new
bugs nor performance issue. This would considered complete when the
ranger is able to fully run using value_range instead of irange.
[snip]
Does this seem reasonable?
I think that's a reasonable pla
On Wed, Jun 5, 2019 at 10:56 PM Andrew MacLeod wrote:
>
> After the various discussions, I've evaluated how I think everything can
> fit together, so this is my proposal for integration with trunk.
>
>
> The complete Ranger prototype consists of 5 major components, one of
> which is missing/un-im
