Displaying 8 results from an estimated 8 matches for "272124".
2016 Jun 08
0
Intended behavior of CGSCC pass manager.
...9;s in the CG and
> ref graph (which the LazyCallGraph API makes one to think about
> since it hides the underlying Tarjan's algorithm).
> The LazyCallGraph API makes the current loop in
> http://reviews.llvm.org/diffusion/L/browse/llvm/trunk/include/llvm/Analysis/CGSCCPassManager.h;272124$100
> very clean, but at least for my thinking about the problem, it seems
> like the wrong abstraction (and most of the LazyCallGraph API seems
> to be unused, so it seems like it may be overly heavyweight).
> E.g. I think that maybe the easiest thing to do is to turn the
> current...
2016 Jun 08
2
Intended behavior of CGSCC pass manager.
...merging SCC's in the CG and ref graph (which the LazyCallGraph API makes one to think about since it hides the underlying Tarjan's algorithm).
> The LazyCallGraph API makes the current loop in http://reviews.llvm.org/diffusion/L/browse/llvm/trunk/include/llvm/Analysis/CGSCCPassManager.h;272124$100 <http://reviews.llvm.org/diffusion/L/browse/llvm/trunk/include/llvm/Analysis/CGSCCPassManager.h;272124$100> very clean, but at least for my thinking about the problem, it seems like the wrong abstraction (and most of the LazyCallGraph API seems to be unused, so it seems like it may be ove...
2016 Jun 08
12
Intended behavior of CGSCC pass manager.
...g and merging SCC's in the CG and ref graph (which the
LazyCallGraph API makes one to think about since it hides the underlying
Tarjan's algorithm).
The LazyCallGraph API makes the current loop in
http://reviews.llvm.org/diffusion/L/browse/llvm/trunk/include/llvm/Analysis/CGSCCPassManager.h;272124$100
very clean, but at least for my thinking about the problem, it seems like
the wrong abstraction (and most of the LazyCallGraph API seems to be
unused, so it seems like it may be overly heavyweight).
E.g. I think that maybe the easiest thing to do is to turn the current
approach inside out: inst...
2016 Jun 08
3
Intended behavior of CGSCC pass manager.
...SCC's in the CG and ref graph (which the LazyCallGraph API makes one to think about since it hides the underlying Tarjan's algorithm).
>>> The LazyCallGraph API makes the current loop in http://reviews.llvm.org/diffusion/L/browse/llvm/trunk/include/llvm/Analysis/CGSCCPassManager.h;272124$100 very clean, but at least for my thinking about the problem, it seems like the wrong abstraction (and most of the LazyCallGraph API seems to be unused, so it seems like it may be overly heavyweight).
>>> E.g. I think that maybe the easiest thing to do is to turn the current approach ins...
2016 Jun 08
2
Intended behavior of CGSCC pass manager.
...d ref graph (which the
>> LazyCallGraph API makes one to think about since it hides the underlying
>> Tarjan's algorithm).
>> The LazyCallGraph API makes the current loop in
>> http://reviews.llvm.org/diffusion/L/browse/llvm/trunk/include/llvm/Analysis/CGSCCPassManager.h;272124$100
>> very clean, but at least for my thinking about the problem, it seems like
>> the wrong abstraction (and most of the LazyCallGraph API seems to be
>> unused, so it seems like it may be overly heavyweight).
>> E.g. I think that maybe the easiest thing to do is to turn t...
2016 Jun 09
2
Intended behavior of CGSCC pass manager.
...gt;> LazyCallGraph API makes one to think about since it hides the underlying
>>>> Tarjan's algorithm).
>>>> The LazyCallGraph API makes the current loop in
>>>> http://reviews.llvm.org/diffusion/L/browse/llvm/trunk/include/llvm/Analysis/CGSCCPassManager.h;272124$100
>>>> very clean, but at least for my thinking about the problem, it seems like
>>>> the wrong abstraction (and most of the LazyCallGraph API seems to be
>>>> unused, so it seems like it may be overly heavyweight).
>>>> E.g. I think that maybe the...
2016 Jun 08
2
Intended behavior of CGSCC pass manager.
...makes one to think about since it hides the
> underlying
> >>>> Tarjan's algorithm).
> >>>> The LazyCallGraph API makes the current loop in
> >>>>
> http://reviews.llvm.org/diffusion/L/browse/llvm/trunk/include/llvm/Analysis/CGSCCPassManager.h;272124$100
> >>>> very clean, but at least for my thinking about the problem, it seems
> like
> >>>> the wrong abstraction (and most of the LazyCallGraph API seems to be
> unused,
> >>>> so it seems like it may be overly heavyweight).
> >>>>...
2016 Jun 16
5
Intended behavior of CGSCC pass manager.
...I makes one to think about since it hides the
>>>>>> underlying Tarjan's algorithm).
>>>>>> The LazyCallGraph API makes the current loop in
>>>>>> http://reviews.llvm.org/diffusion/L/browse/llvm/trunk/include/llvm/Analysis/CGSCCPassManager.h;272124$100
>>>>>> very clean, but at least for my thinking about the problem, it seems like
>>>>>> the wrong abstraction (and most of the LazyCallGraph API seems to be
>>>>>> unused, so it seems like it may be overly heavyweight).
>>>>>&...