diff options
author | Nikita Popov <npopov@redhat.com> | 2023-09-29 14:00:23 +0200 |
---|---|---|
committer | Nikita Popov <npopov@redhat.com> | 2023-10-02 12:40:20 +0200 |
commit | 3b25407d977d9ed3dbcaccd4f8850b65e95d70fd (patch) | |
tree | 8b4d04fb81e7d290608310d28e7dc1791c113a01 /flang/lib/Frontend/CompilerInvocation.cpp | |
parent | 2214026e957397cc6385f778b28d570485a31856 (diff) | |
download | llvm-3b25407d977d9ed3dbcaccd4f8850b65e95d70fd.zip llvm-3b25407d977d9ed3dbcaccd4f8850b65e95d70fd.tar.gz llvm-3b25407d977d9ed3dbcaccd4f8850b65e95d70fd.tar.bz2 |
[IR] Mark zext/sext constant expressions as undesirable
Introduce isDesirableCastOp() which determines whether IR builder
and constant folding should produce constant expressions for a
given cast type. This mirrors what we do for binary operators.
Mark zext/sext as undesirable, which prevents most creations of such
constant expressions. This is still somewhat incomplete and there
are a few more places that can create zext/sext expressions.
This is part of the work for
https://discourse.llvm.org/t/rfc-remove-most-constant-expressions/63179.
The reason for the odd result in the constantexpr-fneg.c test is
that initially the "a[]" global is created with an [0 x i32] type,
at which point the icmp expression cannot be folded. Later it is
replaced with an [1 x i32] global and the icmp gets folded away.
But at that point we no longer fold the zext.
Diffstat (limited to 'flang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions