[llvm-commits] [llvm] r95975 - in /llvm/trunk: include/llvm/Analysis/ lib/Analysis/ lib/CodeGen/ lib/Transforms/Scalar/ test/CodeGen/ARM/ test/CodeGen/Thumb2/ test/CodeGen/X86/ test/Transforms/IndVarSimplify/ test/Transforms/LoopStrengthReduce/

nicolas geoffray nicolas.geoffray at gmail.com
Sun Feb 21 08:28:02 PST 2010


Hey Dan,

Sorry to insist, but I'd really like to see that behavior of always running
the verifier out before llvm 2.7. I understand that it's really useful to
catch bugs
early on, but on the user side, I want to be able to choose if the verifier
runs or not. With your current change it always runs, and that wasn't the
case with the previous releases of llvm.

Now you're developing heavily on LLVM, so I would understand if you reject
my request. But I'd prefer the rejection to be based on a design decision
(the verifier *must* always be run in LLVM) rather than a convenient change
for development of LLVM internal passes. Besides, as Daniel said, you can
run the verifier with any LLVM tool by specifying it on the command line.

Cheers,
Nicolas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20100221/4d55d8b2/attachment.html>


More information about the llvm-commits mailing list