JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for COMP-FORTRAN-90 Archives


COMP-FORTRAN-90 Archives

COMP-FORTRAN-90 Archives


COMP-FORTRAN-90@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

COMP-FORTRAN-90 Home

COMP-FORTRAN-90 Home

COMP-FORTRAN-90  1999

COMP-FORTRAN-90 1999

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Extended precisions

From:

"robin" <[log in to unmask]>

Reply-To:

robin

Date:

Wed, 24 Mar 99 01:32:13 PST

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (77 lines)

				24th March 1999
Pierre Hugonnet wrote:

> Alois Steindl wrote:
> >
> > Hello,
> > let me give it another try:
> > Pierre Hugonnet wrote:
> > >> On a 64bits machine,
> > >>
> > >> REAL(selected_real_kind(p=6)) :: X
> > >> will select the default REAL (precision=15). So the compiler
> > >> will select the default REAL version of MYSUM. In this version
> > >>
> > >> REAL(selected_real_kind(precision(1.0)+1) :: accu
> > >> will select the available 30digits kind (once again assuming that
> > >> nothing exist between 15 and 30). But my original request for
> > >> X was only 6 digits, so that a 12digits (15 in fact on this machine)
> > >> accumulator would fit. Using the 30digits kind in that case
> > >> will waste a lot of CPU (since these kinds are most of time
> > >> emulated) and memory (not a lot here, for a scalar variable :-)).
> > >>
> >
> > Let us assume that 15 and 30 digits are available.
> >
> > I would think that if your X has 6 digits precision and you want 12
> > digits for the accu, then 15 digits for the accu - and also for X -
> > should be sufficient. Can the result be worse than that by using
> > arrays with less precision?
> >
> > If 15 digits is insufficient, you need to use 30 digits for that
> > machine. What's your point?
> >
>
> THE point is the following: on a 64bit machine where the
> smaller precision kind has 15 digits, both
> REAL(selected_real_kind(6)) :: X6
> REAL(selected_real_kind(12)) :: X12
>
> will select in fact the default REAL with 15 digits. At
> this point it of course not a problem. But since the kinds are
> equal, the compiler will call the same version of MYSUM (say
> MYSUM_SINGLE) for both X6 and X12. So in this routine, what
> should be the precision of accu in MYSUM_SINGLE??
> for CALL MYSUM(X6), a REAL accu (15 digits) is sufficient
> for CALL MYSUM(X12), we need a DOUBLE PRECISION (30 digits) accu
>
> Of course, one can use for both cases a 30 digits accu: it
> works but it is not acceptable when processing X6, to use
> an emulated quad precision where a hardware double precision
> would be sufficient.

As it's a 64-bit machine, it will be using single precision for X6,
with a double-precision intermediate summation.  No quadruple precision
is involved.

I think you are confusing with a 32-bit machine.

In the case of a 32-bit machine, only single and double precision would be used
anyway for X6.  On a 32-bit machine, for X12, double and quadruple precision
(if available) would be used.  And in that case, quad precision is necessary.

> The problem is that in MYSUM_SINGLE you have no way to know
> what was the original requested precision of the actual
> argument (X6 or X12).

Is that a problem?  You can distingish the two cases on the number of
arguments.

> Best regards,
> |          Pierre Hugonnet




%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

December 2023
February 2023
November 2022
September 2022
February 2022
January 2022
June 2021
November 2020
September 2020
June 2020
May 2020
April 2020
December 2019
October 2019
September 2019
March 2019
February 2019
January 2019
November 2018
October 2018
September 2018
August 2018
July 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
December 2015
November 2015
October 2015
September 2015
August 2015
June 2015
April 2015
March 2015
January 2015
December 2014
November 2014
October 2014
August 2014
July 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
July 2013
June 2013
May 2013
April 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
August 2010
July 2010
June 2010
March 2010
February 2010
January 2010
December 2009
October 2009
August 2009
July 2009
June 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999
1998
1997


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager