diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2025-04-03 08:32:09 +0200 |
|---|---|---|
| committer | Jakub Jelinek <jakub@gcc.gnu.org> | 2025-04-03 08:32:09 +0200 |
| commit | 1bfc026035e6bade36538077dc1dd4f9baff0bf2 (patch) | |
| tree | 016d65e79f444e56ad5eda60ee134f9a349f891a /gcc/rust/backend/rust-compile-asm.h | |
| parent | 366dd47dc560a37cdf01a4c49a446596564419a0 (diff) | |
| download | gcc-1bfc026035e6bade36538077dc1dd4f9baff0bf2.zip gcc-1bfc026035e6bade36538077dc1dd4f9baff0bf2.tar.gz gcc-1bfc026035e6bade36538077dc1dd4f9baff0bf2.tar.bz2 | |
fold-const, cobol: Add native_encode_wide_int and use it in COBOL FE [PR119242]
As has been mentioned earlier, various parts of the COBOL FE and the library
aren't endian clean. In the library that means that for now we have to
live with no support for big endian targets, but in the FE that means
that as well as not being able to build cross-compilers from big endian
or pdp endian hosts to little endian targets which are otherwise supported.
The following patch attempts to fix one such spot, where it wants to encode
in target byte ordering wide_int constants into 1, 2, 4, 8 or 16 bytes.
We could wide_int_to_tree and then native_encode_expr, but so that we don't
need to build the constants, the following patch exports from fold-const.cc
a helper for native_encode_int which takes type and const wide_int_ref
reference rather than an expression.
2025-04-03 Jakub Jelinek <jakub@redhat.com>
PR cobol/119242
gcc/
* fold-const.h (native_encode_wide_int): Declare.
* fold-const.cc (native_encode_wide_int): New function.
(native_encode_int): Use it.
gcc/cobol/
* genapi.cc (binary_initial_from_float128): Use
native_encode_wide_int.
Diffstat (limited to 'gcc/rust/backend/rust-compile-asm.h')
0 files changed, 0 insertions, 0 deletions