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/60735] GCC targeting E500 with SPE has errors with the _Decimal64 type
Date: Tue, 22 Apr 2014 23:33:00 -0000 [thread overview]
Message-ID: <bug-60735-4-2YFlaWe1gx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60735-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60735
--- Comment #13 from Michael Meissner <meissner at gcc dot gnu.org> ---
Author: meissner
Date: Tue Apr 22 23:33:14 2014
New Revision: 209664
URL: http://gcc.gnu.org/viewcvs?rev=209664&root=gcc&view=rev
Log:
[gcc]
2014-04-21 Michael Meissner <meissner@linux.vnet.ibm.com>
PR target/60735
* config/rs6000/rs6000.md (mov<mode>_softfloat32, FMOVE64 case):
If mode is DDmode and TARGET_E500_DOUBLE allow move.
* config/rs6000/rs6000.c (rs6000_debug_reg_global): Print some
more debug information for E500 if -mdebug=reg.
[gcc/testsuite]
2014-04-21 Michael Meissner <meissner@linux.vnet.ibm.com>
PR target/60735
* gcc.target/powerpc/pr60735.c: New test. Insure _Decimal64 does
not cause errors if -mspe.
Added:
branches/gcc-4_9-branch/gcc/testsuite/gcc.target/powerpc/pr60735.c
- copied unchanged from r209549,
trunk/gcc/testsuite/gcc.target/powerpc/pr60735.c
Modified:
branches/gcc-4_9-branch/gcc/ChangeLog
branches/gcc-4_9-branch/gcc/config/rs6000/rs6000.c
branches/gcc-4_9-branch/gcc/config/rs6000/rs6000.md
branches/gcc-4_9-branch/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2014-04-22 23:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 23:38 [Bug target/60735] New: " meissner at gcc dot gnu.org
2014-04-01 23:42 ` [Bug target/60735] " meissner at gcc dot gnu.org
2014-04-01 23:46 ` meissner at gcc dot gnu.org
2014-04-02 17:04 ` meissner at gcc dot gnu.org
2014-04-02 17:04 ` meissner at gcc dot gnu.org
2014-04-02 17:17 ` meissner at gcc dot gnu.org
2014-04-04 15:14 ` wschmidt at gcc dot gnu.org
2014-04-15 14:12 ` wschmidt at gcc dot gnu.org
2014-04-15 14:12 ` wschmidt at gcc dot gnu.org
2014-04-15 18:20 ` wschmidt at gcc dot gnu.org
2014-04-15 18:25 ` wschmidt at gcc dot gnu.org
2014-04-15 18:30 ` wschmidt at gcc dot gnu.org
2014-04-17 15:57 ` meissner at gcc dot gnu.org
2014-04-21 20:52 ` meissner at gcc dot gnu.org
2014-04-21 22:04 ` meissner at gcc dot gnu.org
2014-04-22 23:33 ` meissner at gcc dot gnu.org [this message]
2014-04-25 16:04 ` wschmidt at gcc dot gnu.org
2014-05-12 23:08 ` bergner 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-60735-4-2YFlaWe1gx@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).