Displaying 4 results from an estimated 4 matches for "invalid_cfg".
Did you mean:
invalid_arg
2013 Jul 22
0
[LLVMdev] Analysis of polly-detect overhead in oggenc
...wing macro combination in function calls:
if (!Context.Verifying) \
++Bad##NAME##ForScop;
So, I do not think it is necessary to translate the INVALID macro into function calls.
Do you still think we should translate INVALID macro into a serial of functions like "invalid_CFG, invalid_IndVar, invalid_IndEdge, ... ? In that case, I could provide a small patch file for this purpose -:)
> 2) Add checks at the beginning of those function calls and
> continue only if LogErrors is set
Those invalid log strings are used for two separate cases:
1) Th...
2013 Jul 22
2
[LLVMdev] Analysis of polly-detect overhead in oggenc
...n in function calls:
> if (!Context.Verifying) \
> ++Bad##NAME##ForScop;
> So, I do not think it is necessary to translate the INVALID macro into function calls.
> Do you still think we should translate INVALID macro into a serial of functions like "invalid_CFG, invalid_IndVar, invalid_IndEdge, ... ? In that case, I could provide a small patch file for this purpose -:)
I think it would still be nice to get rid of this macro. We could
probably have a default function that takes an enum to report different
errors in the reportInvalid(enum errorKind) styl...
2013 Jul 22
2
[LLVMdev] Analysis of polly-detect overhead in oggenc
On 07/21/2013 07:33 PM, Star Tan wrote:
> At 2013-07-22 01:40:31,"Tobias Grosser" <tobias at grosser.es> wrote:
>
>> 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
2013 Jul 23
0
[LLVMdev] Analysis of polly-detect overhead in oggenc
...lls:
>> if (!Context.Verifying) \
>> ++Bad##NAME##ForScop;
>> So, I do not think it is necessary to translate the INVALID macro into function calls.
>> Do you still think we should translate INVALID macro into a serial of functions like "invalid_CFG, invalid_IndVar, invalid_IndEdge, ... ? In that case, I could provide a small patch file for this purpose -:)
>
>I think it would still be nice to get rid of this macro. We could
>probably have a default function that takes an enum to report different
>errors in the reportInvalid(enum...