Re: Are f.p. manipulation functions only used in initialization?
- From: "James Van Buskirk" <not_valid@xxxxxxxxxxx>
- Date: Sat, 26 Apr 2008 20:10:58 -0600
"Anony" <invalid-email@xxxxxxxxxxxx> wrote in message
news:9SOQj.2034$e26.671@xxxxxxxxxxx
On Windows, my result (4.4.0 20080425) is as:
C:\TEMP\fortran>a
ulps1*spacing(x1) = 4.76837158E-07
rrspacing(x1) = 13176795.
scale(x1,ulps1) = 12.566371
set_exponent(x1,ulps1) = 3.1415927
ulps*spacing(x) = 4.76837158E-07
rrspacing(x) = 13176795.
scale(x,ulps) = 12.566371
set_exponent(x,ulps) = 3.1415927
size(j1) = 0
size(j2) = 131
size(j3) = 12
size(j4) = 3
C:\gfortran\james\archpi>c:\gcc_equation\bin\x86_64-pc-mingw32-gfortran -v
Built by Equation Solution (http://www.Equation.com).
Using built-in specs.
Target: x86_64-pc-mingw32
Configured with:
.../gcc-4.4-20080425-mingw/configure --host=x86_64-pc-mingw32 --
build=x86_64-unknown-linux-gnu --target=x86_64-pc-mingw32 --prefix=/home/gfortra
n/gcc-home/binary/mingw32/native/x86_64/gcc/4.4-20080425 --with-gmp=/home/gfortr
an/gcc-home/binary/mingw32/native/x86_64/gmp --with-mpfr=/home/gfortran/gcc-home
/binary/mingw32/native/x86_64/mpfr --with-sysroot=/home/gfortran/gcc-home/binary
/mingw32/cross/x86_64/gcc/4.4-20080425 --with-gcc --with-gnu-ld --with-gnu-as
--
disable-shared --disable-nls --disable-tls --enable-languages=c,fortran --enable
-threads=win32 --enable-libgomp --disable-win32-registry
Thread model: win32
gcc version 4.4.0 20080425 (experimental) (GCC)
C:\gfortran\james\archpi>c:\gcc_equation\bin\x86_64-pc-mingw32-gfortran
spacing_
bug.f90 -ospacing_bug
C:\gfortran\james\archpi>spacing_bug
ulps1*spacing(x1) = 4.76837158E-07
rrspacing(x1) = 13176795.
scale(x1,ulps1) = 12.566371
set_exponent(x1,ulps1) = 3.1415927
ulps*spacing(x) = 2.0000000
rrspacing(x) = 3.1415927
scale(x,ulps) = 3.1415927
set_exponent(x,ulps) = 0.78539819
size(j1) = 2
size(j2) = 0
size(j3) = 3
size(j4) = 0
So I presume your test was carried out on 32-bit Windows. As you
can see, same date build fails on 64-bit Windows. I recall that in
the earliest versions of gfortran for 64-bit Windows, all the single
precision intrinsics were missing. This may be a continuation of
that problem, but now for a subset of intrinsics rather than a
subset of KINDs. Steven Kargl's intuition about platform specificity
seems to have been accurate.
--
write(*,*) transfer((/17.392111325966148d0,6.5794487871554595D-85, &
6.0134700243160014d-154/),(/'x'/)); end
.
- Follow-Ups:
- References:
- Are f.p. manipulation functions only used in initialization?
- From: James Van Buskirk
- Re: Are f.p. manipulation functions only used in initialization?
- From: Anony
- Are f.p. manipulation functions only used in initialization?
- Prev by Date: Re: gfortran produces huge executables
- Next by Date: Re: Are f.p. manipulation functions only used in initialization?
- Previous by thread: Re: Are f.p. manipulation functions only used in initialization?
- Next by thread: Re: Are f.p. manipulation functions only used in initialization?
- Index(es):
Relevant Pages
|
|