Displaying 5 results from an estimated 5 matches for "profitiably".
Did you mean:
profitably
2020 Feb 03
5
Writing loop transformations on the right representation is more productive
Am Do., 30. Jan. 2020 um 04:40 Uhr schrieb Uday Kumar Reddy Bondhugula
<uday at polymagelabs.com>:
> There are multiple ways regions in MLIR can be viewed, but the more relevant point here is you do have a loop tree structure native in the IR with MLIR. Regions in MLIR didn't evolve from modeling inlined calls - the affine.for/affine.if were originally the only two operations in MLIR
2006 Aug 07
0
[LLVMdev] Why JITC?
...a JIT, you can expand
heavily biased calls to test the function pointer (as a validation) and
do a direct call. Then you may be able to inline or IP-constant
propagate the call site. The target of that call site might be input
data based, in which case you cannot statically do these optimizations
profitiably, and even profiling may blur the fact that the call is
mostly static (since different input data may generate different call
targets). Thus you must do runtime profiling and JITing.
Granted, LLVM currently doesn't really do much of this, but the
infastructure is there to do so.
Andrew
2006 Aug 07
4
[LLVMdev] Why JITC?
I guess this is slightly offtopic, but the post about the JIT and garbage
collection made me wonder why LLVM supports JIT compilation at all. It has
much smaller scope for optimisation due to the speed requirements, takes
more memory and causes the same work to be repeated over and over for each
execution.
What reason is there for anything to use JIT compilation over
ahead-of-time compiling to
2020 Jan 30
2
Writing loop transformations on the right representation is more productive
Am Mo., 27. Jan. 2020 um 22:06 Uhr schrieb Uday Kumar Reddy Bondhugula <
uday at polymagelabs.com>:
> Hi Michael,
>
> Although the approach to use a higher order in-memory abstraction like the
> loop tree will make it easier than what you have today, if you used MLIR
> for this representation, you already get a round trippable textual format
> that is *very close* to your
2020 Feb 06
2
Writing loop transformations on the right representation is more productive
On 2/5/20 6:13 PM, Chris Lattner via llvm-dev wrote:
>
>
>> On Feb 2, 2020, at 10:35 PM, Michael Kruse via llvm-dev
>> <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
>>
>>>
>>> That's actually not how I read it. Red/green trees was *one* of the
>>> nine items you mentioned in your list and this didn't