From: Yao Qi <qiyaoltc@gmail.com>
To: Alan Hayward <Alan.Hayward@arm.com>
Cc: "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>,
Subject: Re: [PATCH 2/11] Add IA64_MAX_REGISTER_SIZE
Date: Tue, 25 Apr 2017 16:08:00 -0000 [thread overview]
Message-ID: <86vapsqxld.fsf@gmail.com> (raw)
In-Reply-To: <0CAAE3E4-1860-40FF-895E-6C6A54A4EAB6@arm.com> (Alan Hayward's message of "Wed, 12 Apr 2017 13:41:15 +0000")
Alan Hayward <Alan.Hayward@arm.com> writes:
> @@ -1516,8 +1519,7 @@ examine_prologue (CORE_ADDR pc, CORE_ADDR lim_pc,
> else if (qp == 0 && rN == 2
> && ((rM == fp_reg && fp_reg != 0) || rM == 12))
> {
> - gdb_byte buf[MAX_REGISTER_SIZE];
> - CORE_ADDR saved_sp = 0;
> + ULONGEST saved_sp = 0;
Is it necessary to change the type of "saved_sp"?
> @@ -2490,12 +2488,11 @@ ia64_access_reg (unw_addr_space_t as, unw_regnum_t uw_regnum, unw_word_t *val,
> int write, void *arg)
> {
> int regnum = ia64_uw2gdb_regnum (uw_regnum);
> - unw_word_t bsp, sof, sol, cfm, psr, ip;
> + ULONGEST bsp, sof, cfm, psr, ip;
Why do you change the type?
> struct frame_info *this_frame = (struct frame_info *) arg;
> struct gdbarch *gdbarch = get_frame_arch (this_frame);
> enum bfd_endian byte_order = gdbarch_byte_order (gdbarch);
> long new_sof, old_sof;
> - gdb_byte buf[MAX_REGISTER_SIZE];
>
> /* We never call any libunwind routines that need to write registers. */
> gdb_assert (!write);
> @@ -2570,12 +2561,11 @@ ia64_access_rse_reg (unw_addr_space_t as, unw_regnum_t uw_regnum,
> unw_word_t *val, int write, void *arg)
> {
> int regnum = ia64_uw2gdb_regnum (uw_regnum);
> - unw_word_t bsp, sof, sol, cfm, psr, ip;
> + ULONGEST bsp, sof, cfm, psr, ip;
Likewise.
--
Yao (齐尧)
next prev parent reply other threads:[~2017-04-25 16:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 10:12 Alan Hayward
2017-04-05 10:00 ` Yao Qi
2017-04-11 12:47 ` Alan Hayward
2017-04-11 17:17 ` Yao Qi
2017-04-12 13:41 ` Alan Hayward
2017-04-25 16:08 ` Yao Qi [this message]
2017-04-26 10:38 ` Alan Hayward
2017-04-27 10:17 ` Yao Qi
2017-04-27 10:48 ` Alan Hayward
[not found] ` <79E51549-1B65-4DA8-891A-17EF061E03A3@arm.com>
2017-06-06 10:04 ` Yao Qi
2017-06-06 12:57 ` Alan Hayward
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=86vapsqxld.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=Alan.Hayward@arm.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