Committed as obvious after sanity-checking cris-elf and native x86_64-linux. -- >8 -- There are no messages about padding for targets that don't pad, i.e. default_packed. Noticed for cris-elf, verified for pru-elf at gcc-testresults@.
testsuite: * gcc.dg/plugin/infoleak-vfio_iommu_type1.c: Don't xfail bogus message for "default_packed" targets. --- gcc/testsuite/gcc.dg/plugin/infoleak-vfio_iommu_type1.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/gcc/testsuite/gcc.dg/plugin/infoleak-vfio_iommu_type1.c b/gcc/testsuite/gcc.dg/plugin/infoleak-vfio_iommu_type1.c index 51ad5db2bab2..af320b6b17ee 100644 --- a/gcc/testsuite/gcc.dg/plugin/infoleak-vfio_iommu_type1.c +++ b/gcc/testsuite/gcc.dg/plugin/infoleak-vfio_iommu_type1.c @@ -37,8 +37,8 @@ int vfio_iommu_type1_get_info(unsigned long arg) info.cap_offset = 0; } - /* The padding bytes (20-23) are uninitialized, but can't be written - back, since minsz is either 16 or 20. */ - return copy_to_user((void *)arg, &info, minsz) ? -14 : 0; /* { dg-bogus "exposure" "" { xfail *-*-* } } */ + /* The padding bytes (20-23, but applicable just for targets with padding) are + uninitialized, but can't be written back, since minsz is either 16 or 20. */ + return copy_to_user((void *)arg, &info, minsz) ? -14 : 0; /* { dg-bogus "exposure" "" { xfail { ! default_packed } } } */ // TODO: false +ve due to not handling minsz being either 16 or 20 } -- 2.30.2