Since the _ExtInt type got into the repo, we've discovered that the ABI
implications weren't completely understood. The other architectures are
going to be audited (see D79118), however downstream targets aren't
going to benefit from this audit.
This patch disables the _ExtInt type by default and makes the
target-info an opt-in. As it is audited, I'll re-enable these for all
of our default targets.
return (getPointerWidth(0) >= 64) || getTargetOpts().ForceEnableInt128;
} // FIXME
+ /// Determine whether the _ExtInt type is supported on this target. This
+ /// limitation is put into place for ABI reasons.
+ virtual bool hasExtIntType() const {
+ return false;
+ }
+
/// Determine whether _Float16 is supported on this target.
virtual bool hasLegalHalfType() const { return HasLegalHalfType; }
}
ArrayRef<Builtin::Info> getTargetBuiltins() const override;
+
+ bool hasExtIntType() const override { return true; }
};
class LLVM_LIBRARY_VISIBILITY NetBSDI386TargetInfo
}
ArrayRef<Builtin::Info> getTargetBuiltins() const override;
+
+ bool hasExtIntType() const override { return true; }
};
// x86-64 Windows target
break;
}
case DeclSpec::TST_extint: {
+ if (!S.Context.getTargetInfo().hasExtIntType())
+ S.Diag(DS.getTypeSpecTypeLoc(), diag::err_type_unsupported)
+ << "_ExtInt";
Result = S.BuildExtIntType(DS.getTypeSpecSign() == TSS_unsigned,
DS.getRepAsExpr(), DS.getBeginLoc());
if (Result.isNull()) {
--- /dev/null
+// RUN: %clang_cc1 -triple armv7 -fsyntax-only -verify %s
+
+void foo() {
+ _ExtInt(33) a; // expected-error{{_ExtInt is not supported on this target}}
+}