From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: jan.kratochvil@redhat.com
Cc: siddhesh@redhat.com, binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [patch#2] bfd: Use size_t for length argument totarget_read_memory function passed into bfd_elf_bfd_from_remote_memory
Date: Mon, 04 Jun 2012 06:23:00 -0000 [thread overview]
Message-ID: <201206040622.q546Mqbu026308@ignucius.se.axis.com> (raw)
In-Reply-To: <20120604052438.GA19227@host2.jankratochvil.net> (message from Jan Kratochvil on Mon, 4 Jun 2012 07:24:38 +0200)
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Date: Mon, 4 Jun 2012 07:24:38 +0200
> On Mon, 04 Jun 2012 07:10:18 +0200, Hans-Peter Nilsson wrote:
> > > From: Jan Kratochvil <jan.kratochvil@redhat.com>
> > > Date: Fri, 1 Jun 2012 23:05:30 +0200
> >
> > > bfd/
> > > 2012-06-01 Jan Kratochvil <jan.kratochvil@redhat.com>
> > >
> > > * bfd-in.h (bfd_elf_bfd_from_remote_memory): Make LEN argument
> > > of target_read_memory as bfd_size_type.
> > > * bfd-in2.h: Regenerate.
> > > * elf-bfd.h (elf_backend_bfd_from_remote_memory): Make LEN
> > > argument of target_read_memory as size_t.
> > (..."as bfd_size_type.")
> >
> > > (_bfd_elf32_bfd_from_remote_memory): Likewise.
> > > (_bfd_elf64_bfd_from_remote_memory): Likewise.
> > > * elf.c (bfd_elf_bfd_from_remote_memory): Likewise.
> > > * elfcode.h (NAME(_bfd_elf,bfd_from_remote_memory)): Likewise.
> > >
> > > gdb/
> > > 2012-06-01 Jan Kratochvil <jan.kratochvil@redhat.com>
> > >
> > > * symfile-mem.c: 3 new gdb_static_assert for target_read_memory_bfd
> > > parameters.
> > > (target_read_memory_bfd): New function.
> > > (symbol_file_add_from_memory): Use it.
> >
> > If this is ready to commit and you don't have the time today,
> > just say the word.
>
> I believe I need bfd/ approval by Alan or other bfd/ maintainer.
(I take it all necessary testing is done, then.)
If it'd been me, I'd interpret Alan's: "since Jan has already
given the OK, and these functions are only used by gdb, binutils
maintainers hardly need to look at the patch" (regarding the
earlier corresponding breaking change to size_t) as an intent of
delegation of these bits, but that may be a bit wild. In the
meantime, there's a broken tree.
brgds, H-P
next prev parent reply other threads:[~2012-06-04 6:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 9:05 [PATCH] " Siddhesh Poyarekar
2012-05-28 11:03 ` Alan Modra
2012-05-28 11:11 ` Siddhesh Poyarekar
2012-05-28 21:29 ` Jan Kratochvil
2012-06-01 18:06 ` [commit bfd+gdb] " Jan Kratochvil
2012-06-01 18:24 ` Hans-Peter Nilsson
2012-06-01 19:54 ` Siddhesh Poyarekar
2012-06-01 20:31 ` Jan Kratochvil
2012-06-01 21:05 ` [patch#2] " Jan Kratochvil
2012-06-01 21:21 ` Hans-Peter Nilsson
2012-06-04 5:10 ` Hans-Peter Nilsson
2012-06-04 5:25 ` Jan Kratochvil
2012-06-04 6:23 ` Hans-Peter Nilsson [this message]
2012-06-04 12:11 ` Alan Modra
2012-06-04 14:37 ` [commit] " Jan Kratochvil
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=201206040622.q546Mqbu026308@ignucius.se.axis.com \
--to=hans-peter.nilsson@axis.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=siddhesh@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