public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kkojima at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/53511] SH Target: Add support for fma patterns
Date: Tue, 05 Jun 2012 09:22:00 -0000	[thread overview]
Message-ID: <bug-53511-4-L1rofdJFzN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53511-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Kazumoto Kojima <kkojima at gcc dot gnu.org> 2012-06-05 09:21:49 UTC ---
> It seems that __builtin_sh_media_FMAC_S is broken on trunk
> in the first place, though I can test it only on sh64-elf
> environment now.  Anyway the patch should OK in this regard.

Looking into the __builtin_sh_media_FMAC_S implementation, it takes
2 floating arguments and one return float value.  It looks that
"a = __builtin_sh_media_FMAC_S (b, c)" was expected to work.  I guess
that this is broken in concept.  We can make it take 3 arguments but
I suspect that no one has used it at all.  It might be better to
simply remove this intrinsic because now your patch makes fma usable
naturally.


  parent reply	other threads:[~2012-06-05  9:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-28 22:11 [Bug target/53511] New: " olegendo at gcc dot gnu.org
2012-06-03 16:25 ` [Bug target/53511] " olegendo at gcc dot gnu.org
2012-06-03 18:01 ` olegendo at gcc dot gnu.org
2012-06-03 18:29 ` olegendo at gcc dot gnu.org
2012-06-03 22:48 ` kkojima at gcc dot gnu.org
2012-06-05  2:42 ` olegendo at gcc dot gnu.org
2012-06-05  4:47 ` kkojima at gcc dot gnu.org
2012-06-05  9:22 ` kkojima at gcc dot gnu.org [this message]
2012-06-05 20:08 ` olegendo at gcc dot gnu.org
2012-06-05 20:13 ` olegendo at gcc dot gnu.org
2012-06-05 22:35 ` kkojima at gcc dot gnu.org
2012-06-05 23:06 ` olegendo at gcc dot gnu.org
2012-06-05 23:50 ` kkojima at gcc dot gnu.org
2012-06-11 19:24 ` olegendo at gcc dot gnu.org
2012-06-12 18:26 ` olegendo at gcc dot gnu.org
2012-07-23 22:54 ` olegendo at gcc dot gnu.org
2012-07-23 23:00 ` olegendo 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-53511-4-L1rofdJFzN@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).