aboutsummaryrefslogtreecommitdiff
path: root/gcc/rust
diff options
context:
space:
mode:
authorMarek Polacek <polacek@redhat.com>2023-10-19 16:32:10 -0400
committerMarek Polacek <polacek@redhat.com>2023-10-20 15:32:53 -0400
commit281699fbff6262766674ab13087d37db751cd40a (patch)
tree10f1a33e86ffeaec494812e4f3c03e7195494869 /gcc/rust
parenta663fe63889db486d577b20aff0730034400bfe9 (diff)
downloadgcc-281699fbff6262766674ab13087d37db751cd40a.zip
gcc-281699fbff6262766674ab13087d37db751cd40a.tar.gz
gcc-281699fbff6262766674ab13087d37db751cd40a.tar.bz2
c-family: char8_t and aliasing in C vs C++ [PR111884]
In the PR, Joseph says that in C char8_t is not a distinct type. So we should behave as if it can alias anything, like ordinary char. In C, unsigned_char_type_node == char8_type_node, so with this patch we return 0 instead of -1. And the following comment says: /* The C standard guarantees that any object may be accessed via an lvalue that has narrow character type (except char8_t). */ if (t == char_type_node || t == signed_char_type_node || t == unsigned_char_type_node) return 0; Which appears to be wrong, so I'm adjusting that as well. PR c/111884 gcc/c-family/ChangeLog: * c-common.cc (c_common_get_alias_set): Return -1 for char8_t only in C++. gcc/testsuite/ChangeLog: * c-c++-common/alias-1.c: New test.
Diffstat (limited to 'gcc/rust')
0 files changed, 0 insertions, 0 deletions