From: Jeffrey A Law <law@redhat.com>
To: Cary Coutant <cary@cup.hp.com>
Cc: "Matthew Wilcox" <matthew@wil.cx>,
"Alan Modra" <alan@linuxcare.com.au>,
"Richard Hirst" <rhirst@linuxcare.com>,
parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] parisc64 kernel and ret1 (gr29) setup
Date: Tue, 23 Jan 2001 14:17:48 -0700 [thread overview]
Message-ID: <5101.980284668@slagheap.cygnus.com> (raw)
In-Reply-To: Your message of Tue, 23 Jan 2001 10:47:41 PST. <200101231850.KAA26800@adlmail.cup.hp.com>
In message <200101231850.KAA26800@adlmail.cup.hp.com>you write:
> 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.
Correct. I believe it was roughly 1993 when I first saw the 64byte stack
frame alignment in an ABI spec for 32bit PA/HPUX and twiddled GCC
appropriately.
In 1995 GCC's optimizers were made smarter in terms of removing redundant
pointer arithmetic and logical ops which exposed the fact that hpux wasn't
actually providing a 64byte aligned stack :-) And (of course) I had to
re-adjust the known stack alignment for the PA port to reflect reality.
I haven't looked in any of the newer ABI docs to see if this was ever
corrected.
jeff
next prev parent reply other threads:[~2001-01-23 21:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 18:47 [parisc-linux] parisc64 kernel and ret1 (gr29) setup Cary Coutant
2001-01-23 21:17 ` Jeffrey A Law [this message]
-- 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=5101.980284668@slagheap.cygnus.com \
--to=law@redhat.com \
--cc=alan@linuxcare.com.au \
--cc=cary@cup.hp.com \
--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