Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: remove gnu_debuglink_crc32
Date: Mon, 21 Jan 2013 19:10:00 -0000	[thread overview]
Message-ID: <50FD927F.8030903@redhat.com> (raw)
In-Reply-To: <87sj5u1i08.fsf@fleche.redhat.com>

On 01/21/2013 06:57 PM, Tom Tromey wrote:
> I noticed that BFD has a function equivalent to gnu_debuglink_crc32.
> There doesn't seem to be any reason to keep our own function, so this
> patch removes it.

Right.  GDB gained the function first, and the bfd one was
added afterwards:

http://sourceware.org/ml/binutils/2003-01/msg00511.html

"It has become clear recently that GDB is not the only program which
would benefit from these separate packages; notably objdump and the
oprofile post-processing tools require access to them. Rather than
duplicate the same section-extracting, path-searching and
checksum-matching code in these tools, it was suggested that we
centralize the feature in binutils itself. "

So your patch has been the intention all along.

> 
> Built and regtested on x86-64 Fedora 16.
> 
> There's some other overlap in this area, but I think we can't readily
> share it due to gdb's support of remote files.
> 
> Tom
> 
>     	* symfile.c (get_file_crc): Use bfd_calc_gnu_debuglink_crc32.
>     	* utils.c (gnu_debuglink_crc32): Remove.
>     	* utils.h (gnu_debuglink_crc32): Don't declare.

Looks good to me...

-- 
Pedro Alves


  reply	other threads:[~2013-01-21 19:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-21 18:57 Tom Tromey
2013-01-21 19:10 ` Pedro Alves [this message]
2013-01-30 20:35 ` 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=50FD927F.8030903@redhat.com \
    --to=palves@redhat.com \
    --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