From: Michael Holzheu <holzheu@linux.vnet.ibm.com>
To: "H. Peter Anvin" <hpa@linux.intel.com>
Cc: sam@ravnborg.org, tabbott@ksplice.com, vda.linux@googlemail.com,
mmarek@suse.cz, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, heiko.carstens@de.ibm.com,
brueckner@linux.vnet.ibm.com, schwidefsky@de.ibm.com
Subject: Re: [PATCH] Fix initramfs size calculation
Date: Thu, 26 Aug 2010 10:46:36 +0200 [thread overview]
Message-ID: <1282812396.1879.7.camel@holzheu-laptop> (raw)
In-Reply-To: <4C7578A6.2080303@linux.intel.com>
Hello Peter,
On Wed, 2010-08-25 at 13:10 -0700, H. Peter Anvin wrote:
> On 08/25/2010 08:57 AM, Michael Holzheu wrote:
> > Certain s390 instructions, especially instructions for loading addresses
> > (larl) or branch addresses must be on even addresses.
>
> I have to admit to finding this fairly disturbing, as this is likely to
> come up again and again. Is there any way to tell gcc (e.g. with an
> alignment attribute) that a particular symbol is not safe to be loaded
> with larl?
I think, it is not possible the change that in the compiler. The fact
that the compiler on s390 assumes that symbols are 2 byte aligned was a
design decission and is part of the ABI.
Michael
prev parent reply other threads:[~2010-08-26 8:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 15:57 Michael Holzheu
2010-08-25 18:06 ` Sam Ravnborg
2010-08-25 19:15 ` Hendrik Brueckner
2010-08-25 19:56 ` Sam Ravnborg
2010-08-26 8:55 ` Michael Holzheu
2010-08-26 11:41 ` [PATCH v2 0/2] initramfs: Cleanup and fix " Hendrik Brueckner
2010-08-26 11:41 ` [PATCH v2 1/2] initramfs: Generalize initramfs_data.xxx.S variants Hendrik Brueckner
2010-08-26 11:41 ` [PATCH v2 2/2] initramfs: Fix initramfs size calculation Hendrik Brueckner
2010-08-25 20:10 ` [PATCH] " H. Peter Anvin
2010-08-26 8:46 ` Michael Holzheu [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=1282812396.1879.7.camel@holzheu-laptop \
--to=holzheu@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=brueckner@linux.vnet.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.org \
--cc=schwidefsky@de.ibm.com \
--cc=tabbott@ksplice.com \
--cc=vda.linux@googlemail.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
all inboxes | Powered by JetHome®