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  November 2013

COMP-FORTRAN-90 November 2013

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Should setting an IEEE flag raise the associated exception?

From:

Bill Long <[log in to unmask]>

Reply-To:

Fortran 90 List <[log in to unmask]>

Date:

Tue, 26 Nov 2013 23:59:18 -0600

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (41 lines)

On 11/26/13 2:35 PM, FX wrote:
>> I would expect it to halt, but the standard says "Halting is not precise and may occur any time after the exception has occurred." so I don't think this can be guaranteed.
>
> Yes, I know because of this sentence, halting is not guaranteed. But you’re saying it could happen.
>
>> In section 14.3 of the standard are the words "Each exception has a flag whose value is either quiet or signaling. The value can be determined by the subroutine IEEE_GET_FLAG. Its initial value is quiet and it signals when the associated exception occurs. Its status can also be changed by the subroutine IEEE_SET_FLAG or the subroutine IEEE_SET_STATUS."
>>
>> The intention is to allow the programmer to provoke the same effect as when the hardware signals the condition. Mind you, the usual way to use IEEE_SET_FLAG is to set the flag quiet - I think all the examples in the standard are like this.
>
> My reading was that “[the flag] signals when the associated exception occurs” is an one-sided implication: “exception occurs ==> flag signals”, but nothing specifies that “flags signals ==> exception occurs” (and halting is linked to exceptions occuring, not flags being raised). Thus, halting is not allowed to happen. (Both the Intel and Sun compilers do not halt, as a matter of fact.)
>
> I can’t speak for the intent, though… but if that was the intent, maybe this should be clarified. Does it seem interp-worthy to you? If so, how should I proceed?
>

I tried the test with compilers from multiple vendors, all targeting the 
same hardware (x86_64),  and got a mix of results - some trapped and 
others did not.  Perhaps more interesting, I tried compilers from the 
same vendor targeting two different hardware architectures and had one 
trap and the other not. In the case that trapped, the compiler  had 
inlined the module procedures and the set flag operation was reduced to 
a trivial sequence of instructions that moved the contents of the 
control register to an arithmetic register, OR'ed in the correct bit, 
and then moved the result back to the control register.  Setting the 
control register caused the trap by the hardware since traps for that 
exception had been enabled. That result suggests the "processor 
dependent" answer might be the best we could do.

Cheers,
Bill


> Thanks,
> FX
>

-- 
Bill Long                                           [log in to unmask]
Fortran Technical Support    &                 voice: 651-605-9024
Bioinformatics Software Development            fax:   651-605-9142
Cray Inc./Cray Plaza, Suite 210/380 Jackson St./St. Paul, MN 55101

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