diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2023-09-20 09:45:42 +0200 |
|---|---|---|
| committer | Jakub Jelinek <jakub@redhat.com> | 2023-09-20 09:45:42 +0200 |
| commit | 47ecac52bd4cae84dc786731c655c3bfe1ade377 (patch) | |
| tree | e33dcd0f3f031e22d7568742b9e9727fd64153c3 /gcc/range-op-float.cc | |
| parent | 264ff8182580c57f77c6bc60381cfb2c3842b46c (diff) | |
| download | gcc-47ecac52bd4cae84dc786731c655c3bfe1ade377.zip gcc-47ecac52bd4cae84dc786731c655c3bfe1ade377.tar.gz gcc-47ecac52bd4cae84dc786731c655c3bfe1ade377.tar.bz2 | |
middle-end: use MAX_FIXED_MODE_SIZE instead of precidion of TImode/DImode
On Tue, Sep 19, 2023 at 05:50:59PM +0100, Richard Sandiford wrote:
> How about using MAX_FIXED_MODE_SIZE for things like this?
Seems like a good idea.
The following patch does that.
2023-09-20 Jakub Jelinek <jakub@redhat.com>
* match.pd ((x << c) >> c): Use MAX_FIXED_MODE_SIZE instead of
GET_MODE_PRECISION of TImode or DImode depending on whether
TImode is supported scalar mode.
* gimple-lower-bitint.cc (bitint_precision_kind): Likewise.
* expr.cc (expand_expr_real_1): Likewise.
* tree-ssa-sccvn.cc (eliminate_dom_walker::eliminate_stmt): Likewise.
* ubsan.cc (ubsan_encode_value, ubsan_type_descriptor): Likewise.
Diffstat (limited to 'gcc/range-op-float.cc')
0 files changed, 0 insertions, 0 deletions