public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/29383] Fortran 2003/F95[TR15580:1999]: Floating point exception (IEEE) support Date: Sat, 12 Jun 2010 12:15:00 -0000 [thread overview] Message-ID: <20100612121511.3050.qmail@sourceware.org> (raw) In-Reply-To: <bug-29383-1719@http.gcc.gnu.org/bugzilla/> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 629 bytes --] ------- Comment #4 from burnus at gcc dot gnu dot org 2010-06-12 12:15 ------- Malcolm Cohen wrote in "Implementing the Standards...", http://www.fortran.bcs.org/2007/jubilee/f50.pdf, the following: IEEE module implementation Only if IEEE_GET_FLAG is directly called in a routine: save then clear the flags on entry, merge the flags on exit. Only in a routine that uses a mode setting procedure: save mode on entry, restore mode on exit. Parallelism and other optimisations are little impeded by the use of IEEE facilities (all IEEE semantics being local). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29383
next prev parent reply other threads:[~2010-06-12 12:15 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-10-08 8:41 [Bug fortran/29383] New: " tobias dot burnus at physik dot fu-berlin dot de 2006-10-22 7:20 ` [Bug fortran/29383] " fxcoudert at gcc dot gnu dot org 2009-09-07 8:07 ` burnus at gcc dot gnu dot org 2010-04-14 6:33 ` burnus at gcc dot gnu dot org 2010-06-12 12:15 ` burnus at gcc dot gnu dot org [this message] [not found] <bug-29383-4@http.gcc.gnu.org/bugzilla/> 2011-01-24 9:41 ` thenlich at users dot sourceforge.net 2011-07-22 17:55 ` longb at cray dot com 2012-10-07 0:09 ` kargl at gcc dot gnu.org 2012-10-09 15:19 ` andy.nelson at lanl dot gov 2012-10-09 17:01 ` kargl at gcc dot gnu.org 2012-12-04 19:28 ` quantheory at gmail dot com 2013-04-14 20:09 ` quantheory at gmail dot com 2014-01-06 11:33 ` janus at gcc dot gnu.org 2014-06-03 18:15 ` w6ws at earthlink dot net 2014-06-07 10:19 ` fxcoudert at gcc dot gnu.org 2014-06-07 10:19 ` fxcoudert at gcc dot gnu.org 2014-06-07 10:23 ` fxcoudert at gcc dot gnu.org 2014-06-07 10:25 ` fxcoudert at gcc dot gnu.org 2014-06-15 16:57 ` fxcoudert at gcc dot gnu.org 2014-06-28 14:18 ` fxcoudert at gcc dot gnu.org 2014-06-28 15:11 ` fxcoudert at gcc dot gnu.org 2022-09-10 13:43 ` vital.had at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20100612121511.3050.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).