From: Andreas Schwab <schwab@suse.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: Adam Belay <ambx1@neo.rr.com>, Thomas Hood <jdthood@mail.com>,
linux-kernel@vger.kernel.org
Subject: Re: What exactly is __ALIGN_STR in pnpbios/bioscalls.c for?
Date: Sun, 21 Nov 2004 21:29:32 +0100 [thread overview]
Message-ID: <jefz337xoz.fsf@sykes.suse.de> (raw)
In-Reply-To: <20041121175659.GD2924@stusta.de> (Adrian Bunk's message of "Sun, 21 Nov 2004 18:56:59 +0100")
Adrian Bunk <bunk@stusta.de> writes:
> include/linux/linkage.h in kernel 2.6 includes #define's for __ALIGN and
> __ALIGN_STR. In include/asm-i386/linkage.h, their values are changed
> #ifdef CONFIG_X86_ALIGNMENT_16.
>
> It isn't obvious what exacly CONFIG_X86_ALIGNMENT_16 is for (I've heard
> more than one opinion), and since the __ALIGN_STR usage in
> drivers/pnp/pnpbios/bioscalls.c is the only non-m68k usage of one of
> these two #define's I wonder whether you might be able to enlighten me
> what CONFIG_X86_ALIGNMENT_16 exactly is for?
It's for aligning function entries to a 16 byte boundary instead of only 4
bytes, used together with -malign-functions. See also the ENTRY macro.
Note that the default value of __ALIGN is actually useless for anything
but x86 and x86-64.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2004-11-21 20:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-21 17:56 What exactly is __ALIGN_STR in pnpbios/bioscalls.c for? Adrian Bunk
2004-11-21 20:29 ` Andreas Schwab [this message]
2004-11-21 22:17 ` Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2004-08-06 21:38 Adrian Bunk
2004-01-10 2:22 Adrian Bunk
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=jefz337xoz.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=ambx1@neo.rr.com \
--cc=bunk@stusta.de \
--cc=jdthood@mail.com \
--cc=linux-kernel@vger.kernel.org \
/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.