Displaying 10 results from an estimated 10 matches for "lastfailur".
Did you mean:
lastfailure
2013 Jul 22
0
[LLVMdev] Analysis of polly-detect overhead in oggenc
...t;
>>
>> First, it keeps most of string information by replacing "<<" with "+" operation. For example, code like this:
>> INVALID(CFG, "Non branch instruction terminates BB: " + BB.getName());
>> would be converted into:
>> LastFailure = "Non branch instruction terminates BB: " + BB.getName().str();
>>
>>
>> Second, it simplifies some complex operations like:
>> INVALID(AffFunc,
>> "Non affine branch in BB '" << BB.getName() << "' w...
2013 Jul 21
2
[LLVMdev] Analysis of polly-detect overhead in oggenc
...ng modifications:
>
>
> First, it keeps most of string information by replacing "<<" with "+" operation. For example, code like this:
> INVALID(CFG, "Non branch instruction terminates BB: " + BB.getName());
> would be converted into:
> LastFailure = "Non branch instruction terminates BB: " + BB.getName().str();
>
>
> Second, it simplifies some complex operations like:
> INVALID(AffFunc,
> "Non affine branch in BB '" << BB.getName() << "' with LHS: "
>...
2013 Jul 22
2
[LLVMdev] Analysis of polly-detect overhead in oggenc
...t;> First, it keeps most of string information by replacing "<<" with "+" operation. For example, code like this:
>>> INVALID(CFG, "Non branch instruction terminates BB: " + BB.getName());
>>> would be converted into:
>>> LastFailure = "Non branch instruction terminates BB: " + BB.getName().str();
>>>
>>>
>>> Second, it simplifies some complex operations like:
>>> INVALID(AffFunc,
>>> "Non affine branch in BB '" << BB.getName()...
2013 Jul 22
0
[LLVMdev] Analysis of polly-detect overhead in oggenc
..., it keeps most of string information by replacing "<<" with "+" operation. For example, code like this:
>>>> INVALID(CFG, "Non branch instruction terminates BB: " + BB.getName());
>>>> would be converted into:
>>>> LastFailure = "Non branch instruction terminates BB: " + BB.getName().str();
>>>>
>>>>
>>>> Second, it simplifies some complex operations like:
>>>> INVALID(AffFunc,
>>>> "Non affine branch in BB '" &l...
2013 Jul 21
0
[LLVMdev] Analysis of polly-detect overhead in oggenc
...ile did this work with following modifications:
First, it keeps most of string information by replacing "<<" with "+" operation. For example, code like this:
INVALID(CFG, "Non branch instruction terminates BB: " + BB.getName());
would be converted into:
LastFailure = "Non branch instruction terminates BB: " + BB.getName().str();
Second, it simplifies some complex operations like:
INVALID(AffFunc,
"Non affine branch in BB '" << BB.getName() << "' with LHS: "...
2013 Jul 14
3
[LLVMdev] Analysis of polly-detect overhead in oggenc
On 07/14/2013 08:05 AM, Star Tan wrote:
> I have found that the extremely expensive compile-time overhead comes from the string buffer operation for "INVALID" MACRO in the polly-detect pass.
> Attached is a hack patch file that simply remove the string buffer operation. This patch file can significantly reduce compile-time overhead when compiling big source code. For example, for
2013 Jul 22
2
[LLVMdev] Analysis of polly-detect overhead in oggenc
On 07/22/2013 01:46 AM, Star Tan wrote:
> At 2013-07-22 12:16:53,"Tobias Grosser" <tobias at grosser.es> wrote:
>> I propose two more patches:
>>
>> 1) Transform the INVALID macro into function calls, that format
>> the text and that set LastFailure.
> Translating the INVALID macro into function calls would complicate the operations for different counters.
> For example, currently users can add a new counter by simply adding the following line:
> BADSCOP_STAT(SimpleLoop, "Loop not in -loop-simplify form");
> But if we tr...
2013 Jul 23
0
[LLVMdev] Analysis of polly-detect overhead in oggenc
...01:46 AM, Star Tan wrote:
>> At 2013-07-22 12:16:53,"Tobias Grosser" <tobias at grosser.es> wrote:
>>> I propose two more patches:
>>>
>>> 1) Transform the INVALID macro into function calls, that format
>>> the text and that set LastFailure.
>> Translating the INVALID macro into function calls would complicate the operations for different counters.
>> For example, currently users can add a new counter by simply adding the following line:
>> BADSCOP_STAT(SimpleLoop, "Loop not in -loop-simplify form");
>&...
2013 Jul 16
1
[LLVMdev] Analysis of polly-detect overhead in oggenc
Star Tan wrote:
> I have found that the extremely expensive compile-time overhead comes from the string buffer operation for "INVALID" MACRO in the polly-detect pass.
> Attached is a hack patch file that simply remove the string buffer operation. This patch file can significantly reduce compile-time overhead when compiling big source code. For example, for oggen*8.ll, the compile
2013 Jul 23
2
[LLVMdev] Analysis of polly-detect overhead in oggenc
...\
> - raw_string_ostream fmt(Buf); \
> - fmt << MESSAGE; \
> - fmt.flush(); \
> - LastFailure = Buf; \
> + if (PollyViewMode) { \
I believe this variable should describe what we do, rather than if a
a certain user of this feature is enabled.
Something like
if (TrackFailure...