> and the test runs on powerpc64-linux for both -m32 and -m64. Did
> you have it in a different position? If so I'll try that and see
> if I can figure out why it would be skipped. Also, which target
> were you testing?
I was testing on an IA64 Linux platform (Debian). I had this:
! { dg-do run }
! { dg-additional-sources c_kinds.c }
! { dg-options "-w -std=c99" }
! { dg-require-effective-target stdint_types }
! the -w option is needed to make f951 not report a warning for
! the -std=c99 option that the C file needs.
Maybe I need to move the dg-require-effective-target up?
> Most of the effective target checks use C code. I think it's safe
> to assume that the build or install tree being tested will always
> have a C compiler available.
OK. I wasn't sure if it should work or not. I certainly built C as
well as C++ and Fortran in the build that I was testing.
Steve Ellcey
[EMAIL PROTECTED]
