From: Daniel Jacobowitz <dan@debian.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: robert song <robertsong.linux@gmail.com>, linux-mips@linux-mips.org
Subject: Re: MIPS section alignment of object file
Date: Fri, 22 Feb 2008 14:02:08 -0500 [thread overview]
Message-ID: <20080222190208.GA8697@caradoc.them.org> (raw)
In-Reply-To: <20080222122926.GB17312@linux-mips.org>
On Fri, Feb 22, 2008 at 12:29:26PM +0000, Ralf Baechle wrote:
> The minimum alignment technically required is the largest alignment of
> any type contained in a section. Due to the possibility of relocatable
> links the assembler can't know what the largest aligment is, so it has
> to make a reasonable guess which would be 8 bytes, the size of a double
> floating point.
That's not really true. The compiler is responsible for emitting
appropriate .align directives to communicate this. I don't remember
where the hack in gas came from, but I bet it's required for IRIX.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-02-22 19:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 16:12 MIPS section alignment of object file robert song
2008-02-22 12:29 ` Ralf Baechle
2008-02-22 19:02 ` Daniel Jacobowitz [this message]
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=20080222190208.GA8697@caradoc.them.org \
--to=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=robertsong.linux@gmail.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