public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52258] __builtin_isgreaterequal is sometimes signaling on ARM
Date: Thu, 23 Feb 2012 02:24:00 -0000	[thread overview]
Message-ID: <bug-52258-4-zVP3RS2s0r@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52258-4@http.gcc.gnu.org/bugzilla/>

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

Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2012-02-23
                 CC|                            |ramana at gcc dot gnu.org
      Known to work|                            |4.7.0
     Ever Confirmed|0                           |1
      Known to fail|                            |4.6.3

--- Comment #4 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> 2012-02-23 02:22:28 UTC ---
Fails for anything earlier than trunk strangely enough while 4.6 goes wrong. 

Trunk at O2 appears to generate :

00000000 <main>:
   0:    ed9f 7b13     vldr    d7, [pc, #76]    ; 50 <main+0x50>
   4:    ee87 7b07     vdiv.f64    d7, d7, d7
   8:    b510          push    {r4, lr}
   a:    201f          movs    r0, #31
   c:    b082          sub    sp, #8
   e:    ed8d 7b00     vstr    d7, [sp]
  12:    f7ff fffe     bl    0 <feclearexcept>
  16:    ed9d 7b00     vldr    d7, [sp]
  1a:    eeb5 7b40     vcmp.f64    d7, #0.0
  1e:    eef1 fa10     vmrs    APSR_nzcv, fpscr
  22:    da10          bge.n    46 <main+0x46>
  24:    e9dd 0100     ldrd    r0, r1, [sp]
  28:    f7ff fffe     bl    0 <__isnan>
  2c:    1c04          adds    r4, r0, #0
  2e:    bf18          it    ne
  30:    2401          movne    r4, #1
  32:    2001          movs    r0, #1
  34:    f7ff fffe     bl    0 <fetestexcept>
  38:    b110          cbz    r0, 40 <main+0x40>
  3a:    4807          ldr    r0, [pc, #28]    ; (58 <main+0x58>)
  3c:    f7ff fffe     bl    0 <puts>
  40:    4620          mov    r0, r4
  42:    b002          add    sp, #8
  44:    bd10          pop    {r4, pc}
  46:    2401          movs    r4, #1
  48:    e7f3          b.n    32 <main+0x32>
  4a:    bf00          nop
  4c:    f3af 8000     nop.w
    ...


  parent reply	other threads:[~2012-02-23  2:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-15 10:24 [Bug target/52258] New: " aurelien at aurel32 dot net
2012-02-19 11:31 ` [Bug target/52258] " mikpe at it dot uu.se
2012-02-19 12:23 ` aurelien at aurel32 dot net
2012-02-19 23:49 ` mikpe at it dot uu.se
2012-02-23  2:24 ` ramana at gcc dot gnu.org [this message]
2021-07-19 18:48 ` pinskia at gcc dot gnu.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-52258-4-zVP3RS2s0r@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).