search for: badscop_stat

...orm 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 translate INVALID macro into function calls, then users has to add a function for this counter: void INVLIAD_SimpleLoop (...). This is because we cannot use the following macro combination in function calls: if (!Context.Verify...

...o 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 translate INVALID macro into function calls, then users has to add a function for this counter: > void INVLIAD_SimpleLoop (...). \ ^^ No uppercase in function name...

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

...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 translate INVALID macro into function calls, then users has to add a function for this counter: >> void INVLIAD_SimpleLoop (...). \ > > ^^ No uppercase...