From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: tim@sifive.com (Tim Newsome)
Cc: gdb@sourceware.org (gdb)
Subject: Re: gdbarch_init, ABI, and registers
Date: Sat, 09 Dec 2017 11:27:00 -0000 [thread overview]
Message-ID: <20171209112404.D03C8D80222@oc3748833570.ibm.com> (raw)
In-Reply-To: <CAGDihek6x2QrFBJPHbzA4JxW56wFpAVp_c3CE+EzOjwOoZJhXA@mail.gmail.com> from "Tim Newsome" at Dec 08, 2017 12:03:10 PM
Tim Newsome wrote:
> Am I right in that riscv_gdbarch_init() can differentiate these two cases
> based on whether a target description is passed in or not? Eg. if there is
> a target description, register structures need to be set up, and if there
> isn't then that's not necessary?
Yes, exactly.
> The problem I was seeing is that registers were showing up which shouldn't.
> The reason (as I understand it now) is that I was depending on global
> variables in riscv-tdep.c instead of putting them in gdbarch.data. I'll
> make that change, and hopefully then everything will be better.
I see. Global variables would indeed explain the problem ...
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU/Linux compilers and toolchain
Ulrich.Weigand@de.ibm.com
prev parent reply other threads:[~2017-12-09 11:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 20:21 Tim Newsome
2017-12-07 14:21 ` Handling language trampoline Dmitry Antipov
2017-12-07 14:58 ` Pedro Alves
2017-12-08 6:39 ` Dmitry Antipov
2017-12-08 11:12 ` Pedro Alves
2017-12-07 21:22 ` gdbarch_init, ABI, and registers Tim Newsome
2017-12-08 12:20 ` Ulrich Weigand
2017-12-08 20:03 ` Tim Newsome
2017-12-09 11:27 ` Ulrich Weigand [this message]
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=20171209112404.D03C8D80222@oc3748833570.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb@sourceware.org \
--cc=tim@sifive.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