diff options
author | Peter Waller <peter.waller@arm.com> | 2020-12-10 12:34:00 +0000 |
---|---|---|
committer | Peter Waller <peter.waller@arm.com> | 2020-12-10 12:43:14 +0000 |
commit | 2315e9874c92bf625ec84a5f45a4fa28bfbc16ce (patch) | |
tree | 6f91a22b3cbd2deaaa9598f43656d8c433dd883a /clang/lib/Frontend/CompilerInvocation.cpp | |
parent | 208e3f5d9b6c172f65dbb9cdbc9354c81c6d8911 (diff) | |
download | llvm-2315e9874c92bf625ec84a5f45a4fa28bfbc16ce.zip llvm-2315e9874c92bf625ec84a5f45a4fa28bfbc16ce.tar.gz llvm-2315e9874c92bf625ec84a5f45a4fa28bfbc16ce.tar.bz2 |
[AArch64][Driver][SVE] Push missing SVE feature error from driver to frontend
... and give more guidance to users.
If specifying -msve-vector-bits on a non-SVE target, clang would say:
error: '-msve-vector-bits' is not supported without SVE enabled
1. The driver lacks logic for "implied features".
This would result in this error being raised for -march=...+sve2,
even though +sve2 implies +sve.
2. Feature implication is well modelled in LLVM, so push the error down
the stack.
3. Hint to the user what flag they need to consider setting.
Now clang fails later, when the feature is used, saying:
aarch64-sve-vector-bits.c:42:41: error: 'arm_sve_vector_bits' attribute is not supported on targets missing 'sve'; specify an appropriate -march= or -mcpu=
typedef svint32_t noflag __attribute__((arm_sve_vector_bits(256)));
Move clang/test/Sema/{neon => arm}-vector-types-support.c and put tests for
this warning together in one place.
Reviewed By: sdesmalen
Differential Revision: https://reviews.llvm.org/D92487
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions