Displaying 9 results from an estimated 9 matches for "rdopt".
Did you mean:
adopt
2011 Apr 30
2
[LLVMdev] LoopInfo are not able to identify some natural loops?
Hi,
I found that some loops can not be identified by LoopInfo pass. For example,
the loop at line 3094 of rdopt.c of benchmark 464.h264ref from spec cpu2006
is not a loop or a child (pr grandchild) of any loop in the loop list
generated by LoopInfo pass. The documentation of LoopInfo says that it
identifies natural loops, who have exactly one entry point. But the IR of
this loops shows that it's header o...
2009 Jun 19
2
Changes to Rd handling in R-devel
I've just committed some fairly big changes to R-devel.
- There's a new tag \Sexpr which allows R code to be embedded within
the Rd file, similar to Sweave, \RdOpts
corresponds to \SweaveOpts.
- The parser now mainly issues warnings, rather than errors, in case
of syntax errors. It throws away a few tokens and tries to restart.
This should let you see most of your errors in one pass, rather than one
at a time. (Don't ignore the warnings -- you...
2011 Apr 30
3
[LLVMdev] LoopInfo are not able to identify some natural loops?
...some block outside of the loop jumping to a block in the
> loop body.
>
> Cameron
>
> On Apr 29, 2011, at 7:43 PM, Bo Wu <bwu at cs.wm.edu> wrote:
>
> Hi,
>
> I found that some loops can not be identified by LoopInfo pass. For
> example, the loop at line 3094 of rdopt.c of benchmark 464.h264ref from spec
> cpu2006 is not a loop or a child (pr grandchild) of any loop in the loop
> list generated by LoopInfo pass. The documentation of LoopInfo says that it
> identifies natural loops, who have exactly one entry point. But the IR of
> this loops shows th...
2011 Apr 30
0
[LLVMdev] LoopInfo are not able to identify some natural loops?
...in the loop. There is probably some block outside of the loop jumping to a block in the loop body.
Cameron
On Apr 29, 2011, at 7:43 PM, Bo Wu <bwu at cs.wm.edu> wrote:
> Hi,
>
> I found that some loops can not be identified by LoopInfo pass. For example, the loop at line 3094 of rdopt.c of benchmark 464.h264ref from spec cpu2006 is not a loop or a child (pr grandchild) of any loop in the loop list generated by LoopInfo pass. The documentation of LoopInfo says that it identifies natural loops, who have exactly one entry point. But the IR of this loops shows that it's header o...
2011 May 01
0
[LLVMdev] LoopInfo are not able to identify some natural loops?
...;
> Cameron
>
> On Apr 29, 2011, at 7:43 PM, Bo Wu <bwu at cs.wm.edu
> <mailto:bwu at cs.wm.edu>> wrote:
>
>> Hi,
>>
>> I found that some loops can not be identified by LoopInfo pass.
>> For example, the loop at line 3094 of rdopt.c of benchmark
>> 464.h264ref from spec cpu2006 is not a loop or a child (pr
>> grandchild) of any loop in the loop list generated by LoopInfo
>> pass. The documentation of LoopInfo says that it identifies
>> natural loops, who have exactly one entry point. B...
2017 Aug 25
9
[5.0.0 Release] Release Candidate 3 tagged
Dear testers,
5.0.0-rc3 was just tagged.
This is a release candidate in the real sense: if nothing bad comes up
in testing, this is what the release is going to look like.
Please build, test and upload binaries to the sftp (use the
/data/testers-uploads/ directory) and let me know what issues remain.
I know we're a little bit behind schedule, but hopefully we can get to
'final'
2011 May 01
2
[LLVMdev] LoopInfo are not able to identify some natural loops?
...a block in
>> the loop body.
>>
>> Cameron
>>
>> On Apr 29, 2011, at 7:43 PM, Bo Wu <bwu at cs.wm.edu> wrote:
>>
>> Hi,
>>
>> I found that some loops can not be identified by LoopInfo pass. For
>> example, the loop at line 3094 of rdopt.c of benchmark 464.h264ref from spec
>> cpu2006 is not a loop or a child (pr grandchild) of any loop in the loop
>> list generated by LoopInfo pass. The documentation of LoopInfo says that it
>> identifies natural loops, who have exactly one entry point. But the IR of
>> thi...
2014 Jan 28
3
[LLVMdev] MergeFunctions: reduce complexity to O(log(N))
Hi Stepan,
Sorry for the delay. It's great that you are working on MergeFunctions
as well and I agree, we should definitely try to combine our efforts to
improve MergeFunctions.
Just to give you some context, the pass (with the similar function
merging patch) is already being used in a production setting. From my
point of view, it would be better if we focus on improving its
capability
2014 Jan 30
3
[LLVMdev] MergeFunctions: reduce complexity to O(log(N))
....01 5055 0 0.01 5055
ray.ll 79 139066 5 0.02 139086 2 0.02 139360
rc4.ll 3 19957 0 0.01 19931 0 0.01 19931
rc_quadratic.ll 33 606928 0 0.06 606907 0 0.06 606907
rdbmp.ll 8 101085 0 0.02 101052 0 0.02 101052
rdcolmap.ll 6 48834 0 0.01 48803 0 0.01 48803
rdgif.ll 15 124563 0 0.02 124530 0 0.02 124530
rdopt_coding_state.ll 4 55171 0 0.01 55150 0 0.01 55150
rdopt.ll 36 1039504 0 0.09 1039483 0 0.10 1039483
rdpicdecision.ll 2 29320 0 0.01 29299 0 0.01 29299
rdppm.ll 12 88765 0 0.02 88732 0 0.01 88732
rdrle.ll 0 452 0 0.01 419 0 0.01 419
rdswitch.ll 7 56495 0 0.01 56462 0 0.01 56462
rdtarga.ll 13 92778 0...