From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Kumba <kumba@gentoo.org>, linux-mips@linux-mips.org
Subject: Re: 2.4 kernels + >=binutils-2.14.90.0.8
Date: Tue, 23 Mar 2004 13:00:33 +0100 [thread overview]
Message-ID: <20040323120033.GA6151@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.55.0403221255200.6539@jurand.ds.pg.gda.pl>
On Tue, Mar 23, 2004 at 12:49:02PM +0100, Maciej W. Rozycki wrote:
> > Essentially all platforms that currently set the address to something
> > that's not aligned to a 64kB boundry. I'd like binutils to be fixed
> > instead, though -- I'll try to track the problem down and cook a patch
> > before 2.15. I think the problem may be considered serious enough the
> > release may even be deferred for a few days if necessary (since I believe
> > it's quite close).
>
> After a study of the relevant BFD code, I'm now pretty sure it does its
> job right -- the .text section which is placed at a fixed offset by the
> linker script only imposes an alignment of 4 and the 64kB alignment is
> required by the segment the section is placed in. So BFD does the right
> job by lowering the segment's VMA so that the .text section is placed at
> the requested offset.
>
> What's important, segment alignment happens under the assumption a binary
> will be used in a paged environment. This is not normally the case with a
> MIPS Linux kernel, so I think the right solution is to ask the linker not
> to do page aligning using the "-n" option. Here's a patch that should do
> that.
>
> Ralf, OK to apply this?
Sure, I don't see any possible drawback from this.
Ralf
next prev parent reply other threads:[~2004-03-23 12:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 23:26 2.4 kernels + >=binutils-2.14.90.0.8 Kumba
2004-03-08 23:44 ` Thiemo Seufer
2004-03-09 0:04 ` Kumba
2004-03-09 0:34 ` Thiemo Seufer
2004-03-09 1:08 ` Kumba
2004-03-09 1:38 ` Thiemo Seufer
2004-03-09 2:15 ` Kumba
2004-03-09 2:37 ` Thiemo Seufer
2004-03-09 2:37 ` Thiemo Seufer
2004-03-09 6:07 ` Kumba
2004-03-17 18:51 ` Maciej W. Rozycki
2004-03-17 21:00 ` Kumba
2004-03-17 21:04 ` Maciej W. Rozycki
2004-03-17 23:10 ` Kumba
2004-03-17 23:25 ` Thiemo Seufer
2004-03-17 23:46 ` Maciej W. Rozycki
2004-03-18 0:08 ` Kumba
2004-03-18 0:46 ` Maciej W. Rozycki
2004-03-23 11:49 ` Maciej W. Rozycki
2004-03-23 12:00 ` Ralf Baechle [this message]
2004-03-23 12:50 ` Maciej W. Rozycki
2004-03-23 13:04 ` Ralf Baechle
2004-03-23 14:22 ` Thiemo Seufer
2004-03-09 4:09 ` Ralf Baechle
2004-03-09 6:11 ` Kumba
2004-03-09 15:12 ` Tiago Assumpção
2004-03-09 16:48 ` Ralf Baechle
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=20040323120033.GA6151@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=kumba@gentoo.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.