search for: r186805

...; SCEV <<); >> return false; >> } >> >> I propose to submit such a patch first and then focus on the remaining >> problems. > Yes, I agree with you. I have attached a patch file to move "return false" out of INVALID macro. Great. Committed in r186805. I propose two more patches: 1) Transform the INVALID macro into function calls, that format the text and that set LastFailure. 2) Add checks at the beginning of those function calls and continue only if LogErrors is set The second one is slightly more involved...

...return false; >>> } >>> >>> I propose to submit such a patch first and then focus on the remaining >>> problems. >> Yes, I agree with you. I have attached a patch file to move "return false" out of INVALID macro. > >Great. Committed in r186805. > >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 c...

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 Non-DEBUG mode, so >> TypeFinder is only called in DEBUG mode with the DEBUG

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