zahiraam added inline comments.
================
Comment at: clang/include/clang/Basic/LangOptions.h:300
+ FPP_Fast,
+ FPP_None
+ };
----------------
andrew.w.kaylor wrote:
> Is FPP_None somehow the same as fexcess-precision=16? If not, what does it
> mean?
Yes, maybe this is confusing. How about if we make "none" means disable excess
precision and not use "16"? If you agree with this, then I will edit the
description of the issue above.
================
Comment at: clang/lib/Driver/ToolChains/Clang.cpp:2995
+ StringRef Val = A->getValue();
+ if (TC.getTriple().getArch() == llvm::Triple::x86 && Val.equals("16"))
+ D.Diag(diag::err_drv_unsupported_opt_for_target)
----------------
andrew.w.kaylor wrote:
> Why is 16 only supported for x86? Is it only here for gcc compatibility?
Yes for gcc compatibility (although we are using here that value "none" to
disable excess precision instead of using "16") and also because we are dealing
with excess precision for _Float16 types only, so sticking to X86.
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D136176/new/
https://reviews.llvm.org/D136176
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
