Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Grzegorz Cieslewski" <cieslewski@hcs.ufl.edu>
To: gdb@sourceware.org
Subject: Setting a 128 bit value of the vector register
Date: Tue, 06 Nov 2007 13:46:00 -0000	[thread overview]
Message-ID: <7aa837f80711060545r6f5ba5f5od2370a92c706806b@mail.gmail.com> (raw)

I tried setting the vector register on ppc to a 128 hex number but the
gdb gave me an
"Numeric constant too large".

(gdb) info reg vr1
vr1            {uint128 = 0x00000000000000000000000000000000, v4_float = {
    0x0, 0x0, 0x0, 0x0}, v4_int32 = {0x0, 0x0, 0x0, 0x0}, v8_int16 = {0x0,
    0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v16_int8 = {0x0 <repeats 16 times>}}
(gdb) set $vr0.uint128 = 0xfffffffffffffffff
Numeric constant too large.

I get identical problem when trying to write to an mmx register on
x86.  It happens whenever the number is larger than 64bits

I know that I can brake the number in four peaces up and use
".v4_int32" to accomplish the same goal. I am just wondering if this
is a bug or a "feature".

-- 
=====================================================
Grzegorz Cieslewski
Research Assistant
High-performance Computing & Simulation (HCS) Research Laboratory
University of Florida, Dept. of Electrical and Computer Engineering
330 Benton Hall, Gainesville, FL, 32611-6200
Phone: (352) 392-9041
Email: cieslewski@hcs.ufl.edu
Web: www.hcs.ufl.edu
=====================================================


             reply	other threads:[~2007-11-06 13:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-06 13:46 Grzegorz Cieslewski [this message]
2007-11-06 13:48 ` Daniel Jacobowitz

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=7aa837f80711060545r6f5ba5f5od2370a92c706806b@mail.gmail.com \
    --to=cieslewski@hcs.ufl.edu \
    --cc=gdb@sourceware.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