public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kreckel at ginac dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/29186]  New: optimzation breaks floating point exception flag reading
Date: Fri, 22 Sep 2006 19:13:00 -0000	[thread overview]
Message-ID: <bug-29186-1882@http.gcc.gnu.org/bugzilla/> (raw)

See <http://gcc.gnu.org/ml/gcc-help/2006-09/msg00232.html>.

Disassembling the code suggests that, using gcc-4.1,2, both calls to
fetestexcept(3) mysteriously happened before the division when optimization is
turned on. This was not the case with earlier versions of gcc, where the calls
to fetestexcept(3) bracket the fdivl instruction.


-- 
           Summary: optimzation breaks floating point exception flag reading
           Product: gcc
           Version: 4.1.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: kreckel at ginac dot de
 GCC build triplet: i486-linux-gnu
  GCC host triplet: i486-linux-gnu
GCC target triplet: i486-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29186


             reply	other threads:[~2006-09-22 19:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-22 19:13 kreckel at ginac dot de [this message]
2006-09-22 19:24 ` [Bug c/29186] " pinskia at gcc dot gnu dot org
2006-09-22 19:25 ` pinskia at gcc dot gnu dot org
2006-09-22 19:28 ` pinskia at gcc dot gnu dot org
2006-09-22 22:34 ` kreckel at ginac dot de
2006-09-23 21:41 ` kreckel at ginac dot de
2006-09-23 21:52 ` joseph at codesourcery dot com
2006-09-23 22:11 ` kreckel at ginac dot de
2006-09-23 22:19 ` joseph at codesourcery dot com
2006-09-23 22:58 ` kreckel at ginac dot de
2006-09-23 23:02 ` joseph at codesourcery dot com
2006-09-24  0:35 ` pinskia at gmail dot com
2006-09-24 16:51 ` kreckel at ginac dot de
2006-09-25  7:40 ` kreckel at ginac dot de
2006-10-25  7:54 ` kreckel at ginac dot de
2006-10-25  7:57 ` pinskia at gcc dot gnu dot org
2006-10-25 13:22 ` kreckel at ginac dot de
2006-10-31 11:49 ` kreckel at ginac dot de
2006-11-06 22:23 ` kreckel at ginac dot de
2006-11-19 11:22 ` kreckel at ginac dot de
2006-11-19 12:14 ` rguenth at gcc dot gnu dot org
2009-05-04  6:47 ` kreckel at ginac dot de
2009-12-29 21:48 ` 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=bug-29186-1882@http.gcc.gnu.org/bugzilla/ \
    --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).