[PATCH] Don't try to emit loopVectorize warning if DebugLoc isn't available
Davide Italiano
dccitaliano at gmail.com
Sat May 2 22:54:31 PDT 2015
In http://reviews.llvm.org/D9463#165235, @dexonsmith wrote:
> Would it be better to make emitOptimizationRemarkMissed() resilient to a null DebugLoc? It seems strange to require debug info to print pass remarks.
emitLoopVectorizeWarning() should actually be made resilient because that's where the crash happen.
I'll take a look at this further tomorrow.
REPOSITORY
rL LLVM
http://reviews.llvm.org/D9463
EMAIL PREFERENCES
http://reviews.llvm.org/settings/panel/emailpreferences/
More information about the llvm-commits
mailing list