Displaying 4 results from an estimated 4 matches for "failstring".
Did you mean:
dialstring
2013 Jul 22
0
[LLVMdev] Analysis of polly-detect overhead in oggenc
...c,
LastFailure << "' with LHS: " << *LHS << " and RHS: " << *RHS);
You see, information about LHS and RHS would be kept in INVALID DEBUG information.
To keep the information about unnamed basic blocks, I think we can rewrite it as:
FailString = "Non affine branch in BB: ";
INVALID(AffFunc,
FailString << BB.getName() << "' with LHS: "
<< *LHS << " and RHS: " << *RHS);
LastFailure = FailString + BB.getName().str();
>
>&...
2013 Jul 22
2
[LLVMdev] Analysis of polly-detect overhead in oggenc
...LastFailure << "' with LHS: " << *LHS << " and RHS: " << *RHS);
> You see, information about LHS and RHS would be kept in INVALID DEBUG information.
> To keep the information about unnamed basic blocks, I think we can rewrite it as:
> FailString = "Non affine branch in BB: ";
> INVALID(AffFunc,
> FailString << BB.getName() << "' with LHS: "
> << *LHS << " and RHS: " << *RHS);
> LastFailure = FailString + BB.get...
2013 Jul 21
2
[LLVMdev] Analysis of polly-detect overhead in oggenc
On 07/21/2013 09:49 AM, Star Tan wrote:
> Hi all,
>
>
> I have attached a patch file to reduce the polly-detect overhead.
Great.
> My idea is to avoid calling TypeFinder in Non-DEBUG mode, so
> TypeFinder is only called in DEBUG mode with the DEBUG macro. This
> patch file did this work with following modifications:
>
>
> First, it keeps most of string information
2013 Jul 22
0
[LLVMdev] Analysis of polly-detect overhead in oggenc
...<< "' with LHS: " << *LHS << " and RHS: " << *RHS);
>> You see, information about LHS and RHS would be kept in INVALID DEBUG information.
>> To keep the information about unnamed basic blocks, I think we can rewrite it as:
>> FailString = "Non affine branch in BB: ";
>> INVALID(AffFunc,
>> FailString << BB.getName() << "' with LHS: "
>> << *LHS << " and RHS: " << *RHS);
>> LastFailure = Fai...