aboutsummaryrefslogtreecommitdiff
path: root/binutils/dwarf.c
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2022-02-25 11:03:03 +0000
committerAndrew Burgess <aburgess@redhat.com>2022-03-07 19:42:08 +0000
commitf99e1c6dc8144bfdf1e38b02006a739862a039a3 (patch)
treeb41fcca8df90b4b095f5ec627088a2a67fca2d19 /binutils/dwarf.c
parent551b380fbdad4082bc8520b1b61de883e8e4bf49 (diff)
downloadgdb-f99e1c6dc8144bfdf1e38b02006a739862a039a3.zip
gdb-f99e1c6dc8144bfdf1e38b02006a739862a039a3.tar.gz
gdb-f99e1c6dc8144bfdf1e38b02006a739862a039a3.tar.bz2
gdb/testsuite: add new test for comparing char types in Python
There's an interesting property of the 'char' type in C and C++, the three types 'char', 'unsigned char', and 'signed char', are all considered distinct. In contrast, and 'int' is signed by default, and so 'int' and 'signed int' are considered the same type. This commit adds a test to ensure that this edge case is visible to a user from Python. It is worth noting that for any particular compiler implementation (or the flags a compiler was invoked with), a 'char' will be either signed or unsigned; it has to be one or the other, and a user can access this information by using the Type.is_signed property. However, for something like function overload resolution, the 'char' type is considered distinct from the signed and unsigned variants. There's no change to GDB with this commit, this is just adding a new test to guard some existing functionality.
Diffstat (limited to 'binutils/dwarf.c')
0 files changed, 0 insertions, 0 deletions