From: John Carr <jfc@mit.edu>
To: egcs@cygnus.com
Subject: Re: double alignment patch for x86
Date: Sun, 17 Aug 1997 19:41:24 -0000 [thread overview]
Message-ID: <199708171940.PAA05296@jfc.> (raw)
In-Reply-To: double alignment patch for x86
SPARC has a similar problem -- the calling convention has a maximum 4
byte alignment. 8 byte alignment is desirable (and has always been --
Sun made a bad choice 10 years ago). gcc copies misaligned double
arguments to aligned locations on the stack. Doing this on x86 might
help performance without breaking compatibility (or it might not: on x86
there is only a cost if the dynamic value of the pointer is not aligned
but SPARC requires two instructions instead of one to support possibly
misaligned pointers).
next reply other threads:[~1997-08-17 19:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-17 19:41 John Carr [this message]
1997-08-17 19:41 Marc Lehmann
1997-08-17 21:48 Jeffrey A Law
1997-08-18 14:53 Monday morning Philippe Laliberte
1997-08-18 15:11 ` double alignment patch for x86 Dave Love
1997-08-18 20:46 coxs
1997-08-18 20:47 meissner
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-19 3:24 meissner
1997-08-19 3:52 ` Jeffrey A Law
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=199708171940.PAA05296@jfc. \
--to=jfc@mit.edu \
--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).