public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/37535] gcc/libgcc2.c:404: internal compiler error: Floating point exception
Date: Tue, 16 Sep 2008 02:05:00 -0000	[thread overview]
Message-ID: <20080916020428.5685.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37535-276@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from danglin at gcc dot gnu dot org  2008-09-16 02:04 -------
0x005b7644 <update_copy_costs+308>:     stw r1,-10(sp)
0x005b7648 <update_copy_costs+312>:     fldw -10(sp),fr22R
0x005b764c <update_copy_costs+316>:     cmpiclr,= 0,r10,r0
0x005b7650 <update_copy_costs+320>:     copy r21,r20
0x005b7654 <update_copy_costs+324>:     stw r20,-10(sp)
0x005b7658 <update_copy_costs+328>:     fldw -10(sp),fr22
0x005b765c <update_copy_costs+332>:     xmpyu fr22,fr22R,fr22
0x005b7660 <update_copy_costs+336>:     fstd fr22,-10(sp)
0x005b7664 <update_copy_costs+340>:     ldw -10(sp),r25
0x005b7668 <update_copy_costs+344>:     ldw -c(sp),r26
0x005b766c <update_copy_costs+348>:     b,l 0x5a0cd4,r31
0x005b7670 <update_copy_costs+352>:     nop

The arguments for the multiplication.

(gdb) p/x $r1
$17 = 0x1
(gdb) p/x $r20
$18 = 0xfffffffe

The arguments of the division.

(gdb) p/x $r25
$19 = 0x0
(gdb) p/x $r26
$20 = 0xfffffffe
(gdb) 

Loading r25 from -10(sp) is wierd.


-- 

danglin at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|ice-on-valid-code, ra       |
            Summary|[4.4 Regression]            |gcc/libgcc2.c:404: internal
                   |gcc/libgcc2.c:404: internal |compiler error: Floating
                   |compiler error: Floating    |point exception
                   |point exception             |
   Target Milestone|4.4.0                       |---


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


  parent reply	other threads:[~2008-09-16  2:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-16  0:58 [Bug middle-end/37535] New: " danglin at gcc dot gnu dot org
2008-09-16  1:01 ` [Bug middle-end/37535] [4.4 Regression] " pinskia at gcc dot gnu dot org
2008-09-16  2:05 ` danglin at gcc dot gnu dot org [this message]
2008-09-16  3:37 ` [Bug middle-end/37535] " danglin at gcc dot gnu dot org
2008-09-16  3:42 ` dave at hiauly1 dot hia dot nrc dot ca
2008-09-16 13:04 ` [Bug middle-end/37535] [4.4 Regression] " rguenth at gcc dot gnu dot org
2008-09-16 16:48 ` vmakarov at redhat dot com
2008-09-17  1:11 ` vmakarov at redhat dot com
2008-09-18 12:04 ` krebbel at gcc dot gnu dot org
2008-09-19 23:26 ` vmakarov at gcc dot gnu dot org
2008-09-20 17:06 ` dave at hiauly1 dot hia dot nrc dot ca
2008-09-20 18:45 ` hjl dot tools at gmail dot com
2008-09-21 20:01 ` hjl at gcc dot gnu dot org
2008-09-22 22:47 ` hjl at gcc dot gnu dot org
2008-09-26  0:46 ` vmakarov at gcc dot gnu dot org
2008-09-30  0:39 ` hjl at gcc dot gnu dot org
2008-10-06 15:37 ` vmakarov at gcc dot gnu dot org
2008-10-11 15:12 ` danglin at gcc dot gnu dot org
2008-10-14 22:27 ` hjl at gcc dot gnu dot org
2008-10-16  0:54 ` vmakarov 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=20080916020428.5685.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).