From: "PÃ¥l-Kristian Engstad" <engstad@mail.hunt.inmet.com>
To: Marc Lehmann <pcg@goof.com>, egcs@cygnus.com
Subject: Re: x86 double alignment (was egcs-1.1 release schedule)
Date: Thu, 25 Jun 1998 12:33:00 -0000 [thread overview]
Message-ID: <35929359.562F7F63@hunt.inmet.com> (raw)
In-Reply-To: <19980624192457.45730@cerebro.laendle>
Hi!
Although double-alignment on stack variables would be a bad idea (for
most situations), it would make perfect sense in certain situations.
For instance, leaf functions could certainly benefit from being stack
aligned. Also, functions which only call leaf functions that are stack
aligned can use stack alignment.
Would it be possible to do something like that?
Also, if we are in a situation where we can not stack-align, the
default behaviour for often used variables would be to make a copy
onto the stack (double-aligned), and use this instead (unless it is
only used as a register).
PKE.
next prev parent reply other threads:[~1998-06-25 12:33 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-18 1:32 egcs-1.1 release schedule Jeffrey A Law
1998-06-19 9:02 ` Gerald Pfeifer
1998-06-19 23:47 ` Jeffrey A Law
1998-06-19 11:57 ` Dave Love
1998-06-21 21:43 ` Craig Burley
1998-06-21 23:07 ` Jeffrey A Law
1998-06-22 5:19 ` David S. Miller
1998-06-22 12:04 ` Dave Love
1998-06-22 13:45 ` Toon Moene
1998-06-22 22:29 ` Jeffrey A Law
1998-06-22 18:20 ` ix86 double alignment (was Re: egcs-1.1 release schedule) Craig Burley
1998-06-23 3:32 ` David S. Miller
1998-06-23 6:30 ` Craig Burley
1998-06-23 3:32 ` Jeffrey A Law
1998-06-23 5:13 ` Craig Burley
1998-06-22 12:04 ` egcs-1.1 release schedule Dave Love
1998-06-23 3:32 ` Craig Burley
1998-06-23 3:32 ` Jeffrey A Law
1998-06-23 9:29 ` H.J. Lu
1998-06-24 17:12 ` x86 double alignment (was egcs-1.1 release schedule) Marc Lehmann
1998-06-25 0:25 ` Jeffrey A Law
1998-06-28 18:02 ` Marc Lehmann
1998-06-25 12:33 ` PÃ¥l-Kristian Engstad [this message]
1998-06-28 18:02 ` Marc Lehmann
1998-06-25 21:48 ` Craig Burley
1998-06-25 18:53 ` Jeffrey A Law
1998-06-28 22:41 ` Marc Lehmann
1998-06-29 5:20 ` Martin Kahlert
1998-06-29 11:08 ` Jeffrey A Law
1998-06-29 19:43 ` Craig Burley
1998-06-29 20:41 ` Craig Burley
1998-06-30 0:42 ` Jeffrey A Law
1998-06-30 8:19 ` gcc2 merge H.J. Lu
1998-06-30 19:49 ` Jeffrey A Law
1998-06-30 4:50 ` x86 double alignment (was egcs-1.1 release schedule) Jeffrey A Law
1998-06-22 12:04 ` ix86 `double' alignment (was " Craig Burley
1998-06-23 3:32 ` Jeffrey A Law
1998-06-23 5:13 ` Craig Burley
1998-06-24 2:28 ` Jeffrey A Law
1998-06-24 14:50 ` Craig Burley
1998-06-25 0:25 ` Jeffrey A Law
1998-06-25 9:59 ` Tim Hollebeek
1998-06-28 18:01 ` Marc Lehmann
1998-06-20 6:41 ` egcs-1.1 release schedule Gabriel Dos Reis
1998-06-20 9:22 ` Joe Buck
1998-06-20 15:36 ` Mark Mitchell
1998-06-21 0:07 ` Jeffrey A Law
1998-06-26 7:16 x86 double alignment (was egcs-1.1 release schedule) Michael Meissner
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=35929359.562F7F63@hunt.inmet.com \
--to=engstad@mail.hunt.inmet.com \
--cc=egcs@cygnus.com \
--cc=pcg@goof.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).