public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: Dave Korn <dave.korn@artimi.com>
Cc: binutils@sourceware.org
Subject: Re: Any MIPS experts?
Date: Thu, 22 Sep 2005 19:51:00 -0000	[thread overview]
Message-ID: <20050922154903.GQ3386@hattusa.textio> (raw)
In-Reply-To: <SERRANOKrUV0hCLwHc9000001af@SERRANO.CAM.ARTIMI.COM>

Dave Korn wrote:
> 
> 
> http://sourceware.org/bugzilla/show_bug.cgi?id=702
> 
> 
>   PR702 is about object file bloat introduced in recent binutils versions
> owing to the alignment of one of the sections having been increased from
> 4kB->64kB; the linker is apparently placing explicit padding in the output
> files.  We've been trying to fix this on the crossgcc list[*] without
> success, having tried patches to both gcc[**] and gas[***], and I haven't
> been able to track down any discussion of this issue from the mailing list
> archives.

The .data is placed at some offset in address space (because IRIX did
the same), The introduction of alignment for 64k page size caused then
the preceeding text segment to get padded to the next 64k border instead
of the 4k padding used before.

>   Does any of this ring any bells with MIPS gurus on the list?  Has anyone
> got a fix?  Is it meant to be like this or is it a real bug?

From the ld changelog:

2005-06-01  Maciej W. Rozycki  <macro@linux-mips.org>

	* emulparams/elf32btsmip.sh: Unset DATA_ADDR.
	
This removes the weird separate .data for "traditional" (linux-like)
mips. Also, in some cases ld -N may be acceptable as a workaround for
the problem.


Thiemo

  parent reply	other threads:[~2005-09-22 15:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-22 15:50 Dave Korn
2005-09-22 17:47 ` Mike Frysinger
2005-09-22 19:51 ` Thiemo Seufer [this message]
2005-09-22 22:23   ` Dave Korn
2005-09-23 16:51     ` Maciej W. Rozycki
2005-09-23 18:28       ` Dave Korn
2005-09-23 19:40         ` Maciej W. Rozycki
2005-09-23 20:24           ` Dave Korn
2005-09-26 12:53             ` Maciej W. Rozycki

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=20050922154903.GQ3386@hattusa.textio \
    --to=ths@networkno.de \
    --cc=binutils@sourceware.org \
    --cc=dave.korn@artimi.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).