From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] move gdbarch object from objfile to per-BFD
Date: Tue, 20 Aug 2013 15:01:00 -0000 [thread overview]
Message-ID: <87siy4iexw.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1375734568-31696-1-git-send-email-tromey@redhat.com> (Tom Tromey's message of "Mon, 5 Aug 2013 14:29:28 -0600")
>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
Tom> This moves the "gdbarch" field from the objfile into the BFD.
I'm checking this in now.
Tom
next prev parent reply other threads:[~2013-08-20 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 20:29 Tom Tromey
2013-08-20 15:01 ` Tom Tromey [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2013-08-05 20:12 ` 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=87siy4iexw.fsf@fleche.redhat.com \
--to=tromey@redhat.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