From: "H.J. Lu" <hjl.tools@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>, binutils@sources.redhat.com
Subject: Re: PATCH: PR ld/10569: -z max-page-size may not work for linker scripts
Date: Fri, 28 Aug 2009 08:01:00 -0000 [thread overview]
Message-ID: <6dc9ffc80908272055l3daa1368l1f84cfafcc07c2de@mail.gmail.com> (raw)
In-Reply-To: <6dc9ffc80908272032p5b5a54a6h75caad74a27ffeda@mail.gmail.com>
On Thu, Aug 27, 2009 at 8:32 PM, H.J. Lu<hjl.tools@gmail.com> wrote:
> On Thu, Aug 27, 2009 at 8:14 PM, Alan Modra<amodra@bigpond.net.au> wrote:
>> On Thu, Aug 27, 2009 at 05:02:33PM -0700, H.J. Lu wrote:
>>> PR ld/10569
>>> * ldlang.c (lang_add_output_format): Call
>>> bfd_emul_set_maxpagesize/bfd_emul_set_commonpagesize if
>>> maximum/common page sizes are specified and output target
>>> isn't the same as default target.
>>
>> I think this is the wrong place to call bfd_emul_set_maxpagesize
>> (and the current call in elf32.em is wrong too). You probably should
>> be calling bfd_emul_set_maxpagesize in open_output. Also,
>
> Will open_output be called before any linker scripts are processed?
>
>> bfd_emul_get_maxpagesize in fold_name shouldn't be using
>> default_target. Ditto for commonpagesize.
>>
>
> That is true. I will fix it.
There is no easy fix. Should we just set max/common page sizes for
all enabled ELF targets?
--
H.J.
next prev parent reply other threads:[~2009-08-28 3:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 0:40 H.J. Lu
2009-08-28 3:55 ` Alan Modra
2009-08-28 5:50 ` H.J. Lu
2009-08-28 8:01 ` H.J. Lu [this message]
2009-08-28 8:09 ` Alan Modra
2009-08-28 14:31 ` H.J. Lu
2009-08-28 14:48 ` Alan Modra
2009-08-28 15:05 ` H.J. Lu
2009-08-30 13:51 ` Alan Modra
2009-08-31 2:02 ` H.J. Lu
2009-08-31 2:50 ` Alan Modra
2009-08-31 6:19 ` H.J. Lu
2009-08-31 9:09 ` Alan Modra
2009-08-31 18:16 ` H.J. Lu
2009-09-01 0:00 ` 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=6dc9ffc80908272055l3daa1368l1f84cfafcc07c2de@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=binutils@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).