Re: problem with very small numbers - g95 versus gfortran
- From: "James Van Buskirk" <not_valid@xxxxxxxxxxx>
- Date: Wed, 28 May 2008 21:58:10 -0600
"e p chandler" <epc8@xxxxxxxx> wrote in message
news:9059cf42-b099-4825-990e-fd1b7df9fa09@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Looking up TINY() shows:
TINY(X) returns the smallest positive (non zero) number in the model
of the type of X.
Please explain what I am seeing in light of the above definition. Does
this mean that specifying a literal in double precision where that
literal is less than tiny() is invalid? Yet it seems to work with
gfortran.
At least you found the boundary where the bug is triggered.
I don't have much time, but a description of denormals might perhaps
be found in http://download.intel.com/design/processor/manuals/253665.pdf
section 4.8.3.2. Suffice it to say that denormals aren't model
numbers.
--
write(*,*) transfer((/17.392111325966148d0,6.5794487871554595D-85, &
6.0134700243160014d-154/),(/'x'/)); end
.
- Follow-Ups:
- Re: problem with very small numbers - g95 versus gfortran
- From: e p chandler
- Re: problem with very small numbers - g95 versus gfortran
- References:
- problem with very small numbers - g95 versus gfortran
- From: e p chandler
- Re: problem with very small numbers - g95 versus gfortran
- From: James Van Buskirk
- Re: problem with very small numbers - g95 versus gfortran
- From: e p chandler
- problem with very small numbers - g95 versus gfortran
- Prev by Date: Re: Slick or Slack
- Next by Date: Re: problem with very small numbers - g95 versus gfortran
- Previous by thread: Re: problem with very small numbers - g95 versus gfortran
- Next by thread: Re: problem with very small numbers - g95 versus gfortran
- Index(es):