aboutsummaryrefslogtreecommitdiff
path: root/gcc/rust/backend/rust-compile-struct-field-expr.h
diff options
context:
space:
mode:
authorTom Tromey <tom@tromey.com>2021-06-18 13:13:01 -0600
committerTom Tromey <tom@tromey.com>2021-06-18 13:47:51 -0600
commit231de190d1c8666748eb1c346d22c73946aba743 (patch)
treeaf6862493d16f88c204951bbe2b4e785a6dd715a /gcc/rust/backend/rust-compile-struct-field-expr.h
parente200b89c0f62df1b1dd76c75ccfb90ea82fbb7e5 (diff)
downloadgcc-231de190d1c8666748eb1c346d22c73946aba743.zip
gcc-231de190d1c8666748eb1c346d22c73946aba743.tar.gz
gcc-231de190d1c8666748eb1c346d22c73946aba743.tar.bz2
Use correct DWARF encoding for i8 and u8 types
Currently, the i8 and u8 types use the DWARF character encoding, like: <1><113>: Abbrev Number: 3 (DW_TAG_base_type) <114> DW_AT_byte_size : 1 <115> DW_AT_encoding : 8 (unsigned char) <116> DW_AT_name : u8 This happens because gccrs uses signed_char_type_node and unsigned_char_type_node for i8 and u8, respectively. This patch fixes this problem by arranging to use a custom integer type instead. Another option is to clear TYPE_STRING_FLAG on these types, but it was unclear to me whether this would impact other parts of GCC.
Diffstat (limited to 'gcc/rust/backend/rust-compile-struct-field-expr.h')
0 files changed, 0 insertions, 0 deletions