X-Git-Url: https://oss.titaniummirror.com/gitweb/?a=blobdiff_plain;f=gcc%2Ftestsuite%2Fgcc.c-torture%2Fexecute%2F990826-0.c;fp=gcc%2Ftestsuite%2Fgcc.c-torture%2Fexecute%2F990826-0.c;h=0000000000000000000000000000000000000000;hb=6fed43773c9b0ce596dca5686f37ac3fc0fa11c0;hp=2807ea348eb9ba63a4448be3766587571e6bff75;hpb=27b11d56b743098deb193d510b337ba22dc52e5c;p=msp430-gcc.git diff --git a/gcc/testsuite/gcc.c-torture/execute/990826-0.c b/gcc/testsuite/gcc.c-torture/execute/990826-0.c deleted file mode 100644 index 2807ea34..00000000 --- a/gcc/testsuite/gcc.c-torture/execute/990826-0.c +++ /dev/null @@ -1,27 +0,0 @@ -/* -From: niles@fan745.gsfc.nasa.gov -To: fortran@gnu.org -Subject: Re: Scary problems in g77 for RedHat 6.0. (glibc-2.1) -Date: Sun, 06 Jun 1999 23:37:23 -0400 -X-UIDL: 9c1e40c572e3b306464f703461764cd5 -*/ - -#include -#include - -int -main() -{ - if (floor (0.1) != 0.) - abort (); - return 0; -} - -/* -It will result in 36028797018963968.000000 on Alpha RedHat Linux 6.0 -using glibc-2.1 at least on my 21064. This may result in g77 bug -reports concerning the INT() function, just so you know. - - Thanks, - Rick Niles. -*/