From: "Svein E. Seldal" <Svein.Seldal@solidas.com>
To: gdb@sources.redhat.com
Subject: FP aliases
Date: Wed, 28 May 2003 23:46:00 -0000 [thread overview]
Message-ID: <3ED54A80.3030900@solidas.com> (raw)
Hi,
From the docs in gdb/std-regs.c:75, value_of_builtin_frame_fp_reg() it
states that it will automagically use any registers named "fp" as fp
(instead of using the deprecated fp functions). So what I read is that I
need to reply "fp" in one of the registers in the
set_gdbarch_register_name() function, right?
For my arch, the tic4x, there is no hardware registers named "fp". Is it
wise to replace my "ar3" with "fp". Users will probably get confused
when they are introduced to the "fp" register, as they do not know the
physical relation. But it states that I can create an alias. How? And
why is that dangerous?
I also observere that for the d10v target, no register is named "fp",
but still they manage to do without the the deprecated fp functions. How
is that?
Regards,
Svein
next reply other threads:[~2003-05-28 23:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 23:46 Svein E. Seldal [this message]
2003-05-29 16:11 ` Andrew Cagney
2003-05-29 19:49 ` Svein E. Seldal
2003-05-29 20:01 ` Andrew Cagney
2003-05-29 20:41 ` Svein E. Seldal
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=3ED54A80.3030900@solidas.com \
--to=svein.seldal@solidas.com \
--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).