From: Cary Coutant <cary@cup.hp.com>
To: "Matthew Wilcox" <matthew@wil.cx>, "Alan Modra" <alan@linuxcare.com.au>
Cc: "Richard Hirst" <rhirst@linuxcare.com>,
<parisc-linux@thepuffingroup.com>
Subject: Re: [parisc-linux] parisc64 kernel and ret1 (gr29) setup
Date: Tue, 23 Jan 2001 10:47:41 -0800 [thread overview]
Message-ID: <200101231850.KAA26800@adlmail.cup.hp.com> (raw)
>> Is there any code elsewhere that "knows" the stack frame is 64 bytes
>> (except for gdb and signal handler frames)?
>
>i'm not sure that's the point... knowing the stack frame is 64 byte
>aligned allows the compiler to know the alignment of all types being
>placed on the stack.
On HP-UX, the 64-bit conventions require only 16-byte alignment for stack
frames.
Several years ago we made an attempt to establish a 64-byte stack frame
alignment in the 32-bit conventions, so that the compiler could take
advantage of certain cache hints available on some PA-RISC CPUs. Because
of the complexity of assuring that all stack frames in a program obeyed
this convention, and the growth in average stack use, we abandoned the
idea.
I don't believe, however, that we ever fixed the 32-bit conventions
document to reflect this reversal. Unfortunately, it still says that sp
must be 64-byte aligned. Trust me -- it's wrong. We've never enforced a
64-byte alignment.
-cary
next reply other threads:[~2001-01-23 18:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 18:47 Cary Coutant [this message]
2001-01-23 21:17 ` [parisc-linux] parisc64 kernel and ret1 (gr29) setup Jeffrey A Law
-- strict thread matches above, loose matches on Subject: below --
2000-12-21 16:00 Richard Hirst
2000-12-21 20:57 ` Matthew Wilcox
2000-12-21 20:55 ` Richard Hirst
2001-01-23 13:45 ` Richard Hirst
2001-01-23 14:20 ` Alan Modra
2001-01-23 14:30 ` Matthew Wilcox
2001-01-23 15:43 ` Richard Hirst
2001-02-07 11:18 ` Richard Hirst
2001-02-11 12:09 ` Alan Modra
2001-02-11 23:03 ` Richard Hirst
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=200101231850.KAA26800@adlmail.cup.hp.com \
--to=cary@cup.hp.com \
--cc=alan@linuxcare.com.au \
--cc=matthew@wil.cx \
--cc=parisc-linux@thepuffingroup.com \
--cc=rhirst@linuxcare.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