aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.h
diff options
context:
space:
mode:
authorDavid Green <david.green@arm.com>2023-01-12 18:21:28 +0000
committerDavid Green <david.green@arm.com>2023-01-12 18:21:28 +0000
commit753aca0a3ab0c1822ab3a95beaf8eaa91d7a157d (patch)
treea7e729068e9d59d6dbd24672ebb9675f7ca57a6c /lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.h
parentba35c27ec9aa9807f5b4be2a0c33ca9b045accc7 (diff)
downloadllvm-753aca0a3ab0c1822ab3a95beaf8eaa91d7a157d.zip
llvm-753aca0a3ab0c1822ab3a95beaf8eaa91d7a157d.tar.gz
llvm-753aca0a3ab0c1822ab3a95beaf8eaa91d7a157d.tar.bz2
[AArch64] Add an error if SVE scalable vector types are used in a context without sve
This adds an error message if the isSVESizelessBuiltinType like __SVFloat32_t / __SVInt64_t / etc, which provide the backing for the svfloat32_t / svint64_t / etc ACLE types, are used in a function without SVE. The alternative is a crash in the backend, which is not capable of handling scalable vector types. When SVE is available, either through a -march=..+sve option or via a target(sve) attribute, nothing should change. Without the sve feature, this patch gives an error for any function arguments, return values and variable declarations involving the scalable types. Struct/class members and global variables already give an error. As this can be based on the current function target attributes, the error sometimes needs to be handled later than would otherwise if it was just based on the global target. Differential Revision: https://reviews.llvm.org/D131058
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.h')
0 files changed, 0 insertions, 0 deletions