From: Andi Kleen <ak@muc.de>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Andi Kleen <ak@muc.de>, Paul Wagland <paul@wagland.net>,
linux-kernel@vger.kernel.org, gktnews@gktech.net
Subject: Re: amd64 questions
Date: 7 Apr 2004 20:08:35 +0200
Date: Wed, 7 Apr 2004 20:08:35 +0200 [thread overview]
Message-ID: <20040407180835.GA52759@colin2.muc.de> (raw)
In-Reply-To: <40743110.8000306@nortelnetworks.com>
On Wed, Apr 07, 2004 at 12:49:20PM -0400, Chris Friesen wrote:
> Andi Kleen wrote:
>
> >The problem is always the long long alignment. AMD64/IA64 have different
> >alignment for long long than i386. The emulation was originally tested
> >on some RISC port, where the alignment is the same.
>
> What about a compiler flag to emit i386 code with the more strenuous
> long long alignment?
That would break other things, glibc uses long long heavily too.
The only simple way would be to add the necessary alignment by hand and
create a special 32bit on 64bit kernel iptables or ipsec.
-Andi
next prev parent reply other threads:[~2004-04-07 18:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1Ijzw-4ff-5@gated-at.bofh.it>
[not found] ` <1Ijzv-4ff-3@gated-at.bofh.it>
[not found] ` <1IntE-7wn-39@gated-at.bofh.it>
2004-04-07 16:15 ` amd64 questions Andi Kleen
2004-04-07 16:49 ` Chris Friesen
2004-04-07 18:08 ` Andi Kleen [this message]
2004-04-10 16:54 ` J. Ryan Earl
2004-04-10 18:49 ` Andi Kleen
2004-04-10 19:02 ` Hugo Mills
2004-04-11 11:37 ` Paul Wagland
2004-04-11 11:45 ` Hugo Mills
2004-04-10 20:01 ` J. Ryan Earl
[not found] <1I8up-46J-3@gated-at.bofh.it>
2004-04-07 11:29 ` Andi Kleen
2004-04-07 15:24 ` Paul Wagland
2004-04-07 17:36 ` Bryan Koschmann - GKT
2004-04-06 23:37 Bryan Koschmann - GKT
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=20040407180835.GA52759@colin2.muc.de \
--to=ak@muc.de \
--cc=cfriesen@nortelnetworks.com \
--cc=gktnews@gktech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@wagland.net \
/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 NNTP newsgroup(s).