From: Yao Qi <qiyaoltc@gmail.com>
To: Yan-Ting Lin <currygt52@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] AndesTech NDS32 port
Date: Wed, 01 Jun 2016 11:28:00 -0000 [thread overview]
Message-ID: <868typxi5r.fsf@gmail.com> (raw)
In-Reply-To: <ca473d29-ceb4-ba5e-1337-d479a5f16d8b@gmail.com> (Yan-Ting Lin's message of "Sun, 15 May 2016 17:39:15 +0800")
Yan-Ting Lin <currygt52@gmail.com> writes:
> +enum nds32_regnum
> +{
> + /* General purpose registers. */
> + NDS32_R0_REGNUM = 0,
> + NDS32_R5_REGNUM = 5,
> + NDS32_TA_REGNUM = 15, /* Temporary register. */
> + NDS32_FP_REGNUM = 28, /* Frame pointer. */
> + NDS32_GP_REGNUM = 29, /* Global pointer. */
> + NDS32_LP_REGNUM = 30, /* Link pointer. */
> + NDS32_SP_REGNUM = 31, /* Stack pointer. */
> +
> + NDS32_PC_REGNUM = 32, /* Program counter. */
> +
> + NDS32_NUM_REGS,
> +
> + /* Double precision floating-point registers. */
> + NDS32_FD0_REGNUM = NDS32_NUM_REGS,
> +};
> +
> +struct gdbarch_tdep
> +{
> + /* The guessed FPU configuration. */
> + int fpu_freg;
> + /* FSRs are defined as pseudo registers. */
> + int use_pseudo_fsrs;
> + /* Cached regnum of the first FSR (FS0). */
> + int fs0_regnum;
> + /* Cached regnum of the first FDR (FD0). */
> + int fd0_regnum;
> + /* ABI info. */
> + int abi;
> +};
We can either use NDS32_FD0_REGNUM or gdbarch_tdep.fd0_regnum, IMO. If
the register number of fd0 is fixed, we can use NDS32_FD0_REGNUM,
otherwise, we need to use gdbarch_tdep.fd0_regnum. If so, we can remove
one of them.
--
Yao (齐尧)
next prev parent reply other threads:[~2016-06-01 11:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 7:16 Yan-Ting Lin
2016-05-05 23:46 ` Kevin Buettner
2016-05-06 11:00 ` Yao Qi
2016-05-06 16:09 ` Kevin Buettner
2016-05-09 8:15 ` Yao Qi
2016-05-10 8:45 ` Yan-Ting Lin
2016-05-09 18:33 ` Pedro Alves
2016-05-10 9:31 ` Yan-Ting Lin
2016-05-15 9:39 ` Yan-Ting Lin
2016-06-01 11:28 ` Yao Qi [this message]
2016-06-06 15:13 ` Yan-Ting Lin
2016-06-07 15:34 ` Yao Qi
2016-06-07 16:30 ` Eli Zaretskii
2016-06-08 8:17 ` Yao Qi
2016-06-17 8:08 ` Yan-Ting Lin
2016-06-13 14:12 ` Pedro Alves
2016-06-15 8:44 ` Yan-Ting Lin
2016-06-15 10:07 ` Pedro Alves
2016-06-01 10:52 ` Yao Qi
2016-06-01 11:00 ` Yao Qi
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=868typxi5r.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=currygt52@gmail.com \
--cc=gdb-patches@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).