https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101321
Indu Bhagat <ibhagatgnu at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ibhagatgnu at gmail dot com
--- Comment #5 from Indu Bhagat <ibhagatgnu at gmail dot com> ---
The issue here is in the testcase. It is relying on the order of the generated
CTF types.
Adding -fno-short-enums might have masked the issue, ideally the testcase
should be fixed by removing such a non-portable check.
I noticed similar issues on Darwin for PR debug/101283
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101283
I think the following commit should have fixed this issue on arm-eabi as well.
The master branch has been updated by Indu Bhagat <[email protected]>:
https://gcc.gnu.org/g:d9e9532bb3bf5db4cd6afd49d343ede5b27c3c9f
commit r12-2094-gd9e9532bb3bf5db4cd6afd49d343ede5b27c3c9f
Author: Indu Bhagat <[email protected]>
Date: Tue Jul 6 16:11:47 2021 -0700
BTF testsuite: Remove explicit check on btm_type
The value of btm_type is the BTF type ID of the referred type. The order in
which the BTF types are added can change across platforms and also as the code
evolves, hence changing the BTF type ID. As there is no direct and portable
method of testing that a BTF type refers to another BTF type of a specific
kind, remove the explicit check on btm_type.
This patch adjusts the testcase without affecting the test coverage as other
testcases already have similar constructs. It also fixes a subset of failures
as seen on Darwin.
2021-07-06 Indu Bhagat <[email protected]>
gcc/testsuite/ChangeLog:
PR debug/101283
* gcc.dg/debug/btf/btf-bitfields-3.c: Remove the check on btm_type.
PS: I let -fno-short-enums remain in the testcase for now. If the patch fixes
the issue while removing -fno-short-enums, the testcase can be updated to not
have -fno-short-enums anymore.
