public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joern Wolfgang Rennecke <gnu@amylaar.uk>
To: Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: "Francois.Bedard@synopsys.com" <Francois.Bedard@synopsys.com>,
	"jeremy.bennett@embecosm.com" <jeremy.bennett@embecosm.com>
Subject: Re: [PATCH] [ARC] Add single/double IEEE precission FPU support.
Date: Wed, 10 Feb 2016 06:39:00 -0000	[thread overview]
Message-ID: <56BADB05.4020100@amylaar.uk> (raw)
In-Reply-To: <098ECE41A0A6114BB2A07F1EC238DE8966176790@DE02WEMBXB.internal.synopsys.com>



On 09/02/16 15:34, Claudiu Zissulescu wrote:
> Most of the cases checking only the CC user may be sufficient. However, there are cases (only one which I found), where the CC user has a different mode than of the CC setter.  This is happening when running gcc.dg/pr56424.c test. Here, the C_FPU mode cstore is simplified by the following steps losing the CC_FPU mode:
>
> In the expand:
>     18: cc:CC_FPU=cmp(r159:DF,r162:DF)
>     19: r163:SI=cc:CC_FPU<0
>     20: r161:QI=r163:SI#0
>     21: r153:SI=zero_extend(r161:QI)
>     22: cc:CC_ZN=cmp(r153:SI,0)
>     23: pc={(cc:CC_ZN!=0)?L28:pc}
>
> Then after combine we get this:
>     18: cc:CC_FPU=cmp(r2:DF,r4:DF)
>        REG_DEAD r4:DF
>        REG_DEAD r2:DF
>     23: pc={(cc:CC_ZN<0)?L28:pc}
>        REG_DEAD cc:CC_ZN
>        REG_BR_PROB 6102

That sound like a bug.  Have you looked more closely what's going on?

  reply	other threads:[~2016-02-10  6:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-01 13:58 Claudiu Zissulescu
2016-02-02 22:52 ` Joern Wolfgang Rennecke
2016-02-03 15:02   ` Claudiu Zissulescu
2016-02-03 18:42     ` Joern Wolfgang Rennecke
2016-02-05 14:16   ` Joern Wolfgang Rennecke
2016-02-05 15:54     ` Claudiu Zissulescu
2016-02-09 15:34     ` Claudiu Zissulescu
2016-02-10  6:39       ` Joern Wolfgang Rennecke [this message]
2016-02-10  9:45         ` Claudiu Zissulescu
2016-02-10 12:43         ` Claudiu Zissulescu
2016-02-10 13:31         ` Claudiu Zissulescu
2016-02-12 23:42           ` Joern Wolfgang Rennecke
2016-02-16 14:17             ` Claudiu Zissulescu

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=56BADB05.4020100@amylaar.uk \
    --to=gnu@amylaar.uk \
    --cc=Claudiu.Zissulescu@synopsys.com \
    --cc=Francois.Bedard@synopsys.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeremy.bennett@embecosm.com \
    /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).