public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nasika.srikanth1 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/61979] New: Why float variable loading twice into the FTU Stack during condition checking ?
Date: Thu, 31 Jul 2014 16:52:00 -0000	[thread overview]
Message-ID: <bug-61979-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61979

            Bug ID: 61979
           Summary: Why float variable loading twice into the FTU Stack
                    during condition checking ?
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: other
          Assignee: unassigned at gcc dot gnu.org
          Reporter: nasika.srikanth1 at gmail dot com

Actually its not a bug. But i identified that float variables are loading twice
into the FTU STACK during the condition checking ,that's actually my doubt and
i check without loading it again i remove repeated code and getting the same
output . But why gcc complier loads the float variable again into the FTU Stack
? For checking the condition it first  checks the parity flags(whether NAN ,INF
)then it again loads the float variable into FTU stack and check for the zero
flag( whether non zero) set or not. But  we can directly check the zero flag
after checking parity flag  with out loading the variable into the FTU stack.


             reply	other threads:[~2014-07-31 16:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-31 16:52 nasika.srikanth1 at gmail dot com [this message]
2014-08-01  8:26 ` [Bug other/61979] " rguenth at gcc dot gnu.org
2014-08-02  6:19 ` nasika.srikanth1 at gmail dot com
2014-08-02  6:37 ` [Bug other/61979] Why float variable loading twice into the FPU " nasika.srikanth1 at gmail dot com
2014-08-02  6:42 ` pinskia at gcc dot gnu.org
2014-08-02 11:12 ` nasika.srikanth1 at gmail dot com
2014-08-02 11:33 ` glisse at gcc dot gnu.org
2014-08-02 16:29 ` nasika.srikanth1 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=bug-61979-4@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).