Typically statx always denotes the function and struct statx denotes the struct.
When usage of the struct is encountered in C++ code, abi-compliance-checker generates this line in dump1.h:
statx* tmp_add_class_66;
which fails to compile:
/tmp/qktDQcucCm/dump1.h:103:3: error: 'statx' does not name a type
statx* tmp_add_class_66;
^~~~~
Ideally abi-compliance-checker should instead generate this in dump1.h:
struct statx* tmp_add_class_66;
but determining when the struct qualifier should/shouldn't be used seems non-trivial, so lets take the same approach as we do for other similarly overloaded names.
statx (like stat, wait, flock, sysinfo) is both the name of a function:
and a struct:
Typically
statx
always denotes the function andstruct statx
denotes the struct.When usage of the struct is encountered in C++ code, abi-compliance-checker generates this line in dump1.h:
which fails to compile:
Ideally abi-compliance-checker should instead generate this in dump1.h:
but determining when the
struct
qualifier should/shouldn't be used seems non-trivial, so lets take the same approach as we do for other similarly overloaded names.