From: Doug Evans <dje@google.com>
To: xingxing pan <forandom@gmail.com>
Cc: gdb <gdb@sourceware.org>
Subject: Re: Which version of binutils matches the BFD and Opcode in GDB6.8?
Date: Tue, 15 Sep 2009 15:47:00 -0000 [thread overview]
Message-ID: <e394668d0909150846k7b12ad1ub5a9b2eabdd8dab7@mail.gmail.com> (raw)
In-Reply-To: <77f815bd0909150638s49b0ce27g722a005384f495a6@mail.gmail.com>
[repeating for the list's sake]
Like I said, they come from the same source tree so there is only one
bfd/opcode from a source tree point of view.
And collectively we (gdb people + binutils people) maintain that source tree
(though there are many who work on both).
But since gdb and binutils are on different release schedules, you
can't necessarily match the copies of bfd/opcodes in each. If
binutils/gdb are released at similar times, the differences will be
small but not necessarily identical.
For completeness' sake,
Procedurally, bfd/opcodes patches go to the binutils mailing list,
they "own" bfd/opcodes.
On Tue, Sep 15, 2009 at 6:38 AM, xingxing pan <forandom@gmail.com> wrote:
> You mean there are two groups of people maintain the bfd/opcode
> respectively? Why not use one bfd/opcode? What's the difference?
>
> 2009/9/15 Doug Evans <dje@google.com>:
>> On Tue, Sep 15, 2009 at 6:19 AM, xingxing pan <forandom@gmail.com> wrote:
>>> Are the BFD and Opcode in GDB6.8 from the binutils or developed
>>> separately from binutils?
>>
>> Depends on what you mean by "separate". :-)
>>
>> They do come from the same source tree, and so are not separate in
>> that sense, *but* they are released at different times, and so one
>> can't, technically, match bfd/opcodes from a binutils release with the
>> ones in a gdb release.
>>
>
prev parent reply other threads:[~2009-09-15 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 13:19 xingxing pan
2009-09-15 13:24 ` Doug Evans
2009-09-15 13:38 ` xingxing pan
2009-09-15 15:47 ` Doug Evans [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=e394668d0909150846k7b12ad1ub5a9b2eabdd8dab7@mail.gmail.com \
--to=dje@google.com \
--cc=forandom@gmail.com \
--cc=gdb@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