From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC: Add 'double' member to 64-bit vector register type
Date: Sat, 19 Mar 2005 15:37:00 -0000 [thread overview]
Message-ID: <20050319153709.GA4659@nevyn.them.org> (raw)
In-Reply-To: <vt2is3omadg.fsf@zenia.home>
On Sat, Mar 19, 2005 at 01:13:15AM -0500, Jim Blandy wrote:
>
> gdb/ChangeLog:
> 2005-03-17 Jim Blandy <jimb@redhat.com>
>
> * gdbtypes.c (build_builtin_type_vec64): Include a 'double' member
> in the union, too, since these registers can hold 64-bit floating
> point types.
Rationale belongs in the patch mail or in comments, not in the
changelog.
I suppose you might as well, since no one but the e500 uses them. But
only some SPE processors support the double precision mode; do you
really want to display the register as double on e500 v1?
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-03-19 15:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-19 6:17 Jim Blandy
2005-03-19 15:37 ` Daniel Jacobowitz [this message]
2005-03-19 21:17 ` Jim Blandy
2005-03-20 2:33 ` Daniel Jacobowitz
2005-03-20 11:14 ` Mark Kettenis
2005-04-05 16:58 ` Jim Blandy
2005-04-06 7:09 ` Mark Kettenis
2005-04-07 5:00 ` Jim Blandy
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=20050319153709.GA4659@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.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