From: David Edelsohn <dje.gcc@gmail.com>
To: Michael Meissner <meissner@linux.vnet.ibm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix PR 60203: No direct move support for long double/_Decimal128 on powerpc ISA 2.07
Date: Sat, 15 Feb 2014 00:43:00 -0000 [thread overview]
Message-ID: <CAGWvnympXraw7CBznEqF-zoXs+hdmsGhQx7gYmmQEbb2tymrXw@mail.gmail.com> (raw)
In-Reply-To: <20140214225948.GA18526@ibm-tiger.the-meissners.org>
On Fri, Feb 14, 2014 at 5:59 PM, Michael Meissner
<meissner@linux.vnet.ibm.com> wrote:
> When I added direct move support for ISA 2.07 (power8), I did not add direct
> move support for long double and _Decimal128 types. This patch adds the direct
> move support for those types when you are running in 64-bit mode. Now, there
> are still the problems raised in PR 25972 on machines without direct move, but
> this simple patch does help the machines with direct move.
>
> I bootstrapped the compiler with/without the change, and there were no
> regressions in the test suite. Is it ok to check into the tree?
>
> [gcc]
> 2014-02-14 Michael Meissner <meissner@linux.vnet.ibm.com>
>
> PR target/60203
> * config/rs6000/rs6000.md (rreg): Add TFmode, TDmode constraints.
> (mov<mode>_internal, TFmode/TDmode): Split TFmode/TDmode moves
> into 64-bit and 32-bit moves. On 64-bit moves, add support for
> using direct move instructions on ISA 2.07. Also adjust
> instruction length for 64-bit.
> (mov<mode>_64bit, TFmode/TDmode): Likewise.
> (mov<mode>_32bit, TFmode/TDmode): Likewise.
>
> [gcc/testsuite]
> 2014-02-14 Michael Meissner <meissner@linux.vnet.ibm.com>
>
> PR target/60203
> * gcc.target/powerpc/pr60203.c: New testsuite.
Okay.
Thanks, David
prev parent reply other threads:[~2014-02-15 0:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 22:59 Michael Meissner
2014-02-14 23:10 ` Michael Meissner
2014-02-15 0:43 ` David Edelsohn [this message]
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=CAGWvnympXraw7CBznEqF-zoXs+hdmsGhQx7gYmmQEbb2tymrXw@mail.gmail.com \
--to=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=meissner@linux.vnet.ibm.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).