public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/30780] cpu_time produces a floating point exception when used with -O0
Date: Tue, 13 Feb 2007 04:32:00 -0000 [thread overview]
Message-ID: <20070213043231.5731.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30780-14089@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from pinskia at gcc dot gnu dot org 2007-02-13 04:32 -------
I have no idea how to fix this problem at the moment.
It is hard as there are no functions which convert from a floating point to an
integer that might not raise a signal. This is why setting trapping on
precision is almost something you never want to do.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|fortran |libfortran
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30780
next prev parent reply other threads:[~2007-02-13 4:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-12 21:08 [Bug fortran/30780] New: " glv at maths dot otago dot ac dot nz
2007-02-12 21:26 ` [Bug fortran/30780] " pinskia at gcc dot gnu dot org
2007-02-12 21:28 ` pinskia at gcc dot gnu dot org
2007-02-13 4:26 ` kargl at gcc dot gnu dot org
2007-02-13 4:32 ` pinskia at gcc dot gnu dot org [this message]
2007-02-13 5:41 ` [Bug libfortran/30780] " jvdelisle at gcc dot gnu dot org
2007-02-13 6:41 ` kargl at gcc dot gnu dot org
2007-02-14 0:37 ` jvdelisle at gcc dot gnu dot org
2007-09-21 11:37 ` [Bug libfortran/30780] FPE in CPU_TIME (and possibly others) with -ffpe-trap=underflow fxcoudert at gcc dot gnu dot org
2007-09-21 11:45 ` burnus at gcc dot gnu dot org
2007-09-21 11:59 ` fxcoudert at gcc dot gnu dot org
2007-09-26 22:27 ` fxcoudert at gcc dot gnu dot org
2007-09-26 22:28 ` fxcoudert at gcc dot gnu dot org
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=20070213043231.5731.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: link
Be 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).