Re: [Patch][LoopVectorize] Late evaluate of runtime pointer check's threshold

2015-08-10 Thread Hal Finkel via cfe-commits
- Original Message - > From: "Tyler Nowicki" > To: "Hal Finkel" > Cc: "Gerolf Hoflehner" , "Commit Messages and Patches > for LLVM" , > "llvm cfe" > Sent: Monday, August 10, 2015 6:06:24 PM > Subject: Re: [Patc

Re: [Patch][LoopVectorize] Late evaluate of runtime pointer check's threshold

2015-08-10 Thread Tyler Nowicki via cfe-commits
Hi Hal, Thanks, the patches are committed in r244523 and r244526. There are two possibilities to give the user control over pointer checking. We could add a loop hint option like vectorize(check_safety) that would be a safe version of ‘assume_safety’ or we could simply make it always emit the n

Re: [Patch][LoopVectorize] Late evaluate of runtime pointer check's threshold

2015-08-09 Thread Hal Finkel via cfe-commits
Hi Tyler, This looks very useful. Please don't mention '-mllvm -runtime-memory-check-threshold=' in the error message. We should add some clause to #pragma clang loop to control this feature with some associated metadata. '-mllvm' things should not be part of the advertised interface to end us