From: Hans-Peter Nilsson <hp@bitrange.com>
To: Alan Modra <amodra@gmail.com>
Cc: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: vdso handling
Date: Wed, 02 Apr 2014 08:04:00 -0000 [thread overview]
Message-ID: <alpine.BSF.2.02.1404020356460.33178@arjuna.pair.com> (raw)
In-Reply-To: <20140328061321.GU18201@bubble.grove.modra.org>
On Fri, 28 Mar 2014, Alan Modra wrote:
>
> bfd_from_remote_memory should take note of p_memsz.. Hmm, and there
> are quite a few other issues there too, most notably that p_align
> on x86_64 these days tends to be *much* larger than the page size used
> by ld.so.
>
> Gah, I've been sucked into looking at this long enough that I may as
> well fix it. Does this look OK?
The new size parameter uses size_t in bfd headers, breaking some
simulators like cris-elf, frv-elf, h8300-elf, iq2000-elf,
m32r-elf, mips-elf, mn10300-elf.
The obvious change is to instead use bfd_size_type, like
everything else in BFD headers. Any reason not to do that here?
> * elfcode.h (bfd_from_remote_memory): Add "size" parameter.
brgds, H-P
next prev parent reply other threads:[~2014-04-02 8:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140313130322.GA3384@bubble.grove.modra.org>
[not found] ` <5321C7C8.6000707@redhat.com>
[not found] ` <5321C8FA.40708@gmail.com>
[not found] ` <5321CE1A.20509@redhat.com>
[not found] ` <20140313235347.GD3384@bubble.grove.modra.org>
[not found] ` <A78C989F6D9628469189715575E55B230AAB6B17@IRSMSX103.ger.corp.intel.com>
[not found] ` <20140318230939.GA9145@bubble.grove.modra.org>
[not found] ` <5329879C.6070805@redhat.com>
[not found] ` <20140320013305.GA13347@bubble.grove.modra.org>
[not found] ` <532C5F60.80700@redhat.com>
2014-03-28 6:13 ` Alan Modra
2014-03-28 13:38 ` Pedro Alves
2014-03-28 23:00 ` Alan Modra
2014-04-01 13:46 ` Pedro Alves
2014-04-02 1:50 ` Alan Modra
2014-04-02 8:05 ` Metzger, Markus T
2014-04-02 8:04 ` Hans-Peter Nilsson [this message]
2014-04-03 1:06 ` Alan Modra
2014-04-03 1:46 ` Alan Modra
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=alpine.BSF.2.02.1404020356460.33178@arjuna.pair.com \
--to=hp@bitrange.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--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