public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/22473] FAIL: gcc.c-torture/execute/conversion.c execution -O[012]
Date: Sat, 14 Jan 2012 07:20:00 -0000 [thread overview]
Message-ID: <bug-22473-4-Te67uIkecW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-22473-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22473
--- Comment #4 from John David Anglin <danglin at gcc dot gnu.org> 2012-01-14 04:54:23 UTC ---
This is a binutils bug. Single word conversions need to
use the 0E opcode rather than the 0C opcode that's currently
generated for fcnv,t,sgl,uwd.
This doesn't fail for PA1.1 because the instruction isn't
available. On the 64-bit target, the right half of the
floating point register is always used for word operands
forcing the 0E opcode.
next prev parent reply other threads:[~2012-01-14 4:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-22473-4@http.gcc.gnu.org/bugzilla/>
2012-01-11 14:09 ` rguenth at gcc dot gnu.org
2012-01-11 14:55 ` dave.anglin at bell dot net
2012-01-13 23:22 ` danglin at gcc dot gnu.org
2012-01-14 7:20 ` danglin at gcc dot gnu.org [this message]
2012-01-14 23:50 ` danglin at gcc dot gnu.org
2012-01-15 19:10 ` danglin 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-22473-4-Te67uIkecW@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).