This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Committed: g++.dg/abi/empty6.C: Xfail warning for mmix-*-*. PRtarget/18484.


A larger requested alignment may be appropriate, but how large?
(Author!)

	PR target/18484
	* g++.dg/abi/empty6.C: Xfail warning for mmix-*-*.

Index: empty6.C
===================================================================
RCS file: /cvs/gcc/gcc/gcc/testsuite/g++.dg/abi/empty6.C,v
retrieving revision 1.2
diff -p -c -r1.2 empty6.C
*** empty6.C	3 Jun 2003 19:10:09 -0000	1.2
--- empty6.C	28 Nov 2004 23:23:39 -0000
***************
*** 3,13 ****
  struct A {};

  struct B {
!   A a; // { dg-warning "empty" }
    virtual void f () {}
  } __attribute__((aligned(8)));
  /* The preceding attribute is necessary on targets with
     BIGGEST_ALIGNMENT <= 32 to trigger the warning, as otherwise a 32 bit
     offset is split into DECL_FIELD_OFFSET 4 and DECL_FIELD_BIT_OFFSET 0,
     and then there is no discrepancy between DECL_FIELD_OFFSET and
!    byte_position to warn about.  */
--- 3,15 ----
  struct A {};

  struct B {
!   A a; // { dg-warning "empty" "" { xfail mmix-*-* } }
    virtual void f () {}
  } __attribute__((aligned(8)));
  /* The preceding attribute is necessary on targets with
     BIGGEST_ALIGNMENT <= 32 to trigger the warning, as otherwise a 32 bit
     offset is split into DECL_FIELD_OFFSET 4 and DECL_FIELD_BIT_OFFSET 0,
     and then there is no discrepancy between DECL_FIELD_OFFSET and
!    byte_position to warn about.
!    On the other hand 64-bit targets for example, generally need a larger
!    requested alignment to get the intended warning.  */

brgds, H-P


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]