From: Elena Zannoni <ezannoni@redhat.com>
To: "Martin M. Hunt" <hunt@redhat.com>
Cc: Elena Zannoni <ezannoni@redhat.com>, gdb@sources.redhat.com
Subject: Re: [RFC] Simplify SIMD registers
Date: Mon, 29 Apr 2002 08:51:00 -0000 [thread overview]
Message-ID: <15565.27620.331459.734991@localhost.redhat.com> (raw)
In-Reply-To: <Pine.SOL.3.91.1020427225229.14088B-100000@makita.cygnus.com>
Martin M. Hunt writes:
> On Fri, 26 Apr 2002, Elena Zannoni wrote:
>
> > Now, I have concerns for platforms other than Altivec, that may have
> > used a representation like the one I would like to abandon.
> > I am talking about SSE regs on x86 which are v4sf type. Right?
>
> SSE registers are v4sf only, but SSE2 registers (Pentium 4) are
> v2df, v4sf, v16qi, v8hi, v4si, and v2di. I don't believe GDB supports
> them yet.
>
Ah ok, so those could be supported w/o structure wrappers. But the
debug format is only stabs on x86, and we don't set the flags for those
types to TYPE_VECTOR. If we did that we could avoid the structures.
>
> > For this reason I didn't touch the existing built in types which have
> > the structure wrapping, but I introduced new ones to be used by
> > AltiVec registers.
> >
> > Comments?
>
> I would like to see us treat all SIMD registers in the same manner, not
> just Altivec. Even though the packing and size will vary, the display
> syntax should be consistent.
>
Yes, I would like this too.
Any opinions from the x86 aficionados? Eli? Daniel? Mark?
> Martin
Elena
next prev parent reply other threads:[~2002-04-29 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-26 19:35 Elena Zannoni
2002-04-27 23:06 ` Martin M. Hunt
2002-04-29 8:51 ` Elena Zannoni [this message]
2002-04-29 9:08 ` Elena Zannoni
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=15565.27620.331459.734991@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=hunt@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