eandrews added a comment.
This has changed the behavior for -
// Define __complex128 type corresponding to __float128 (as in GCC headers).
typedef _Complex float __attribute__((mode(TC))) __complex128;
void check() {
// CHECK: alloca { fp128, fp128 } <----- Fails because alloca { x86_fp80,
x86_fp80 } is generated instead
__complex128 tmp;
}
In TargetInfo.cpp, we used to check long double format to decide whether to
return LongDouble or Float128. This patch doesn't, and so the return value has
changed from FloatModeKind::Float128 to clang::FloatModeKind::LongDouble
(ExplicitType). Should we be checking the format?
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D109950/new/
https://reviews.llvm.org/D109950
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
