From: Andi Kleen <andi@firstfloor.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andi Kleen <andi@firstfloor.org>, "H.J. Lu" <hjl.tools@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: PATCH] Use -mpreferred-stack-boundary=3 on x86-64 if supported
Date: Sat, 23 Jun 2012 21:27:04 +0200 [thread overview]
Message-ID: <20120623192704.GT11413@one.firstfloor.org> (raw)
In-Reply-To: <24bd04a1-1702-4d57-af64-af2381992789@email.android.com>
On Sat, Jun 23, 2012 at 09:17:06AM -0700, H. Peter Anvin wrote:
> To keep gcc from paddong the stack to maintain a nonexistent alignment.
Ah ok. 3 instead of 4.
I thought i had done that a long time ago, but now it somehow
only seems to be there for 32bit.
Makes sense.
-Andi
next prev parent reply other threads:[~2012-06-23 19:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 16:06 PATCH] Use -mpreferred-stack-boundary=3 on x86-64 if supported H.J. Lu
2012-06-23 16:13 ` Andi Kleen
2012-06-23 16:17 ` H. Peter Anvin
2012-06-23 16:49 ` H.J. Lu
2012-06-23 22:57 ` Randy Dunlap
2012-06-23 19:27 ` Andi Kleen [this message]
2012-06-23 19:45 ` H. Peter Anvin
2012-06-24 3:13 ` [tip:x86/build] x86-64, gcc: Use -mpreferred-stack-boundary= 3 " tip-bot for H.J. Lu
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=20120623192704.GT11413@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox