From: Jason Molenda <jmolenda@apple.com>
To: "Décio Luiz Gazzoni Filho" <decio@decpp.net>
Cc: gdb@sources.redhat.com
Subject: Re: Altivec doesn't work?
Date: Tue, 19 Jul 2005 03:39:00 -0000 [thread overview]
Message-ID: <28363812-BF6A-4ECA-A1E7-264C1280249D@apple.com> (raw)
In-Reply-To: <859254B0-0A3D-4AA1-80F9-1DCE4354E866@decpp.net>
Daniel was correct that this isn't the right forum for Apple gdb
questions. Please send these kinds of things to xcode-
users@lists.apple.com.
You'll want to be more specific about your program that isn't working
under gdb. For instance, this works fine with gdb-413:
#include <altivec.h>
int main () {
vector unsigned int x = ((vector unsigned int) vec_splat_u8 (-2));
}
(gdb) p/x x
$2 = {0xfefefefe, 0xfefefefe, 0xfefefefe, 0xfefefefe}
(gdb)
Please follow up on xcode-users@ if you have any questions or
problems with the Apple tools. Thanks!
Jason
On Jul 16, 2005, at 11:00 AM, Décio Luiz Gazzoni Filho wrote:
> Hello,
>
> I have `GNU gdb 6.1-20040303 (Apple version gdb-413)' running on
> Mac OS X 10.4.2. I wrote some Altivec code and tried to load it
> into gdb. Although gdb can print the vector registers, they are not
> updated by any instructions that are run: all regs stay at the
> value 0x7FFFDEAD7FFFDEAD7FFFDEAD7FFFDEAD.
>
> I believe it's not a compilation issue, or a processor issue (mine
> is an MPC7447). Outside of gdb, the code seems to run fine (doesn't
> give an invalid instruction exception).
>
> This is my first foray into Altivec programming, so I'm wondering
> what I'm missing here? This can't be a bug as Google doesn't turn
> anything up.
>
> Décio
next prev parent reply other threads:[~2005-07-19 3:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-16 18:04 Décio Luiz Gazzoni Filho
2005-07-16 18:11 ` Daniel Jacobowitz
2005-07-19 3:39 ` Jason Molenda [this message]
2005-07-19 3:44 ` Décio Luiz Gazzoni Filho
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=28363812-BF6A-4ECA-A1E7-264C1280249D@apple.com \
--to=jmolenda@apple.com \
--cc=decio@decpp.net \
--cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).