From: "Andreas Tobler" <[EMAIL PROTECTED]>
Hi Kaveh,
[...]
Hm, there is no iso/math_c99.h and I guess the reason is here:
From the /usr/include/iso/math_c99.h
#pragma ident "@(#)math_c99.h 1.12 07/01/21 SMI"
From the fixincl.x:
tSCC zSolaris_Math_1Select0[] =
"@\\(#\\)math_c99.h[ \t]+1.[0-9]+[ \t]+[0-9/]+ SMI";
From my quick view I'd say we do not match the 1.12, we're only able to
handle 1.0-9 right?
I don't think that's it. The pattern is "1.[0-9]+" and the plus regexp
should match one or more digits. So it should match "1.12".
I notice that the solaris_math_* fix hacks all seems to have a bypass clause
on "GNUC". Sometimes the solaris headers try to be gcc-aware. Is there a
GNUC appearing in solaris11's /usr/include/iso/math_c99.h header? And that
begs the question, why do these fix hacks have this GNUC bypass in the first
place?
I'll see if I'm wrong.
And for the failing part for example:
c99-math-double-1.c:18
nan = nan(0x8000000000000)
inf = 0
huge = 0
norm1 = 2.2250738585072014e-308
norm2 = 1
norm3 = 1.7976931348623157e+308
sub = 1.1125369292536007e-308
zero = 0
Thanks but I meant: of the many if-aborts, which is triggered when running
under gdb? That will tell us which builtin is failing. (May be they all
are.) I don't know what the header looks like to know what if anything
should be changed by fixincludes.
--Kaveh
--
Kaveh R. Ghazi
