bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: m4 tests failed


From: Piotr Tarnowski
Subject: Re: m4 tests failed
Date: Fri, 28 Sep 2007 09:45:28 +0200
User-agent: Thunderbird 1.5.0.13 (X11/20070824)

Eric Blake napisaƂ(a):
> Please keep replies on the list, so that others can pitch in.

OK

> This one may already be fixed in CVS.  At any rate, could you run 'cd
> tests; sh -vx ./test-closein.sh' so we can make sure where it is failing?
> 

Result is in attachement.

>> cc: Warning: -xarch=native has been explicitly specified, or implicitly
> specified by a macro option, -xarch=native on this architecture implies
> -xarch=sparcvis2 which generates code that does not run on pre UltraSPARC
> III processors
>> configure:2920: $? = 0
> 
> I bet that warning gets annoying after a while.

Yes, it is.

> So, based on your compiler complaints, it appears that it has a C99 mode,
> but that we don't know the magic to turn it on.  Can you investigate what
> compiler flag is necessary to get c99 enabled on your setup?  (At least
> the gnulib stdbool replacement worked).

The flag is -xc99=o
where o is separated list of:
          [no]_lib       [Do not] Enable the 1999 C standard
                         library semantics of routines that
                         appeared in both the 1990 and 1999 C
                         standard.

          all            Turn on recognition of supported C99
                         language features and enable the 1999 C
                         standard library semantics of routines
                         that appear in both the 1990 and 1999 C
                         standard.

          none           Turn off recognition of C99 language
                         features, and do not enable the 1999 C
                         standard library semantics of routines
                         that appeared in both the 1990 and 1999
                         C standard.

          If you do not specify -xc99, the compiler defaults to
          -xc99=all,no_lib.

          If you specify -xc99 without any values, the option is
          set to -xc99=all.

> So, configure detected that printf supports long double, but not infinite
> long double.  What does this program do for you?
> 
> #include <stdio.h>
> int main() {
>   printf("%g %d\n", (long double) 1.5, 33);
> }

wega% cc test1.c
wega% ./a.out
-2.24632e+307 -13033472

wega% cc -fast test1.c
cc: Warning: -xarch=native has been explicitly specified, or implicitly
specified by a macro option, -xarch=native on this architecture implies
-xarch=sparcvis2 which generates code that does not run on pre
UltraSPARC III processors
wega% ./a.out
-2.24631e+307 -13033472

wega% cc -fast -xautopar test1.c
cc: Warning: -xarch=native has been explicitly specified, or implicitly
specified by a macro option, -xarch=native on this architecture implies
-xarch=sparcvis2 which generates code that does not run on pre
UltraSPARC III processors
wega% ./a.out
-2,24631e+307 -14737408

wega% c99 test1.c
wega% ./a.out
-2.24632e+307 -13033472

wega% CC test1.c
wega% ./a.out
-2.24634e+307 -14848432

BTW: When I turned off parallelization (removed -xautopar) all tests was
successful
===================
All 36 tests passed
===================

Regards.
-- 
Piotr




reply via email to

[Prev in Thread] Current Thread [Next in Thread]