public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/60203] Support long double/_Decimal128 direct move on power8 Date: Wed, 19 Feb 2014 02:23:00 -0000 [thread overview] Message-ID: <bug-60203-4-KFtlRIJbtC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60203-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60203 --- Comment #7 from Michael Meissner <meissner at gcc dot gnu.org> --- Author: meissner Date: Wed Feb 19 02:23:10 2014 New Revision: 207869 URL: http://gcc.gnu.org/viewcvs?rev=207869&root=gcc&view=rev Log: 2014-02-18 Michael Meissner <meissner@linux.vnet.ibm.com> PR target/60203 * config/rs6000/rs6000.md (mov<mode>_64bit, TF/TDmode moves): Split 64-bit moves into 2 patterns. Do not allow the use of direct move for TDmode in little endian, since the decimal value has little endian bytes within a word, but the 64-bit pieces are ordered in a big endian fashion, and normal subreg's of TDmode are not allowed. (mov<mode>_64bit_dm): Likewise. (movtd_64bit_nodm): Likewise. Modified: branches/ibm/gcc-4_8-branch/gcc/ChangeLog.ibm branches/ibm/gcc-4_8-branch/gcc/config/rs6000/rs6000.md
prev parent reply other threads:[~2014-02-19 2:23 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-14 18:37 [Bug target/60203] New: " meissner at gcc dot gnu.org 2014-02-14 18:39 ` [Bug target/60203] " meissner at gcc dot gnu.org 2014-02-14 23:03 ` meissner at gcc dot gnu.org 2014-02-16 3:08 ` meissner at gcc dot gnu.org 2014-02-16 3:10 ` meissner at gcc dot gnu.org 2014-02-16 3:19 ` meissner at gcc dot gnu.org 2014-02-19 2:14 ` meissner at gcc dot gnu.org 2014-02-19 2:23 ` meissner at gcc dot gnu.org [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=bug-60203-4-KFtlRIJbtC@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: linkBe 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).