It looks like we don't do anything special if you run clang-cl -O0 or /O0,
but it's not an error. I don't have my computer and can't run a test, but
from the outside, it looks like clang-cl -O0 does generate unoptimized code
without warning about an unrecognized flag, but it doesn't disable FP
The generic O flag handling doesn't support 0 either. Would you be ok with
removing this?
Does /Od do what you want?
On Wed, Sep 19, 2018 at 4:52 PM Reid Kleckner
wrote:
> I was probably using it myself, and was surprised that /O0 and -O0 had
> different behavior, because -O0 will hit the
