diff options
| author | Tamar Christina <tamar.christina@arm.com> | 2025-08-19 10:15:54 +0100 |
|---|---|---|
| committer | Tamar Christina <tamar.christina@arm.com> | 2025-08-19 10:15:54 +0100 |
| commit | 4982644625dc5a46e959ecf8167641f6ae21f76d (patch) | |
| tree | 31e92f1abb692a5bd8df329f3a018a6b12fe705e /libgfortran/generated/shape_i16.c | |
| parent | 8c2b3377a28b55279cabf586547cf25c0734d563 (diff) | |
| download | gcc-4982644625dc5a46e959ecf8167641f6ae21f76d.zip gcc-4982644625dc5a46e959ecf8167641f6ae21f76d.tar.gz gcc-4982644625dc5a46e959ecf8167641f6ae21f76d.tar.bz2 | |
AArch64: Fix scalar costing after removal of vectype from mid-end [PR121536]
commit g:fb59c5719c17a04ecfd58b5e566eccd6d2ac583a stops passing the scalar type
(confusingly named vectype) to the costing hook when doing scalar costing.
As a result, we could no longer distinguish between FPR and GPR scalar stmts.
A later commit also removed STMT_VINFO_VECTYPE from stmt_info.
This leaves the only remaining option to get the type of the original stmt in
the stmt_info. This patch does this when we're performing scalar costing.
Ideally I'd refactor this a bit because a lot of the hooks just need to know if
it's FP or not, but this seems pointless with the ongoing costing churn. So for
now this restores our costing.
gcc/ChangeLog:
PR target/121536
* config/aarch64/aarch64.cc (aarch64_vector_costs::add_stmt_cost): Set
vectype from type of lhs of gimple stmt.
Diffstat (limited to 'libgfortran/generated/shape_i16.c')
0 files changed, 0 insertions, 0 deletions