From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: tromey@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] move gdbarch object from objfile to per-BFD
Date: Mon, 05 Aug 2013 19:22:00 -0000 [thread overview]
Message-ID: <201308051922.r75JMD4p020143@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <877gg07xz4.fsf@fleche.redhat.com> (message from Tom Tromey on Mon, 05 Aug 2013 13:13:03 -0600)
> From: Tom Tromey <tromey@redhat.com>
> Cc: gdb-patches@sourceware.org
>
> >>>>> "Mark" == Mark Kettenis <mark.kettenis@xs4all.nl> writes:
>
> Mark> The pointer chasing gets a bit ridiculous though. Perhaps it needs a
> Mark> little helper function?
>
> I can add it. The reason I did not is that, for whatever reason,
> objfiles have not historically used accessors. So, I preserved the
> status quo in this respect.
Merely a suggestion. If you considered it and decided against it
that's fine with me.
next prev parent reply other threads:[~2013-08-05 19:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 17:56 Tom Tromey
2013-08-05 18:11 ` Mark Kettenis
2013-08-05 19:13 ` Tom Tromey
2013-08-05 19:22 ` Mark Kettenis [this message]
2013-08-05 20:12 ` Tom Tromey
2013-08-05 20:29 Tom Tromey
2013-08-20 15:01 ` Tom Tromey
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=201308051922.r75JMD4p020143@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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