From: Jeffrey A Law <law@hurl.cygnus.com>
To: egcs@cygnus.com
Subject: Re: double alignment patch for x86
Date: Tue, 19 Aug 1997 03:52:10 -0000 [thread overview]
Message-ID: <199708190343.XAA13881@tweedledumb.cygnus.com> (raw)
Message-ID: <19970819035210.6LwX3sik6weFIzDTc8Jxt2aAeyw9J1kk2t5ED6KOzso@z> (raw)
In-Reply-To: double alignment patch for x86
In message <199708190343.XAA13881@tweedledumb.cygnus.com>you write:
> | That's one way to approach the problem, but it results in an extra insn t
> o
> | mask off the low bits of the stack in the prologue.
>
> I meant just raise STACK_ALIGNMENT to 64. Aligning it at runtime would
> be a disaster on the x86, due to all arguments being pushed on the stack,
> and having few registers.
Oh. Slight mis-communication.
However, raising STACK_ALIGNMENT would still lose if the OS and friends
don't keep the stack suitably aligned -- some of Kenner's changes from last
year in combine.c will blow up badly (see REG_POINTER_ALIGNMENT changes from
1996).
I had the distinct pleasure of analyzing half a dozen of these kinds of
problems because the ABI on the PA specifies a 64byte alignment, but the
OS+crt0.o only provides an 8 byte alignment. The result was combine
would remove instructions it throught were redundant, but which were
really necessary.
jeff
next reply other threads:[~1997-08-19 3:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-19 3:24 meissner [this message]
1997-08-19 3:52 ` Jeffrey A Law
-- strict thread matches above, loose matches on Subject: below --
1997-08-19 2:36 2 (small?) problems Ian Lance Taylor
1997-08-19 3:24 ` double alignment patch for x86 Jeffrey A Law
1997-08-18 20:47 meissner
1997-08-18 20:46 coxs
1997-08-18 14:53 Monday morning Philippe Laliberte
1997-08-18 15:11 ` double alignment patch for x86 Dave Love
1997-08-17 21:48 Jeffrey A Law
1997-08-17 19:41 Marc Lehmann
1997-08-17 19:41 John Carr
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=199708190343.XAA13881@tweedledumb.cygnus.com \
--to=law@hurl.cygnus.com \
--cc=egcs@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).