public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Stan Cox <scox@cygnus.com>
Cc: egcs@cygnus.com
Subject: Re: x86 alignment stuff
Date: Sun, 22 Feb 1998 18:48:00 -0000	[thread overview]
Message-ID: <6298.888202223@hurl.cygnus.com> (raw)
In-Reply-To: <nrra4vp32s.fsf_-_@rtl.cygnus.com>

  In message < nrra4vp32s.fsf_-_@rtl.cygnus.com >you write:
  > >Does anybody know why we don't items in the static store on the
  > >x86?  Seems to me we can align stuff in the static store via
  > >DATA_ALIGNMENT and friends without breaking ABI compatability.
  >  
  > The x86 ABI alignment is: char (1), short (2), int/long/enum (4),
  > *type (4), float (4), double (4), long double (4).
  > double and long double are of course the interesting ones.
Those specify minimum alignments.  What I'm looking for is any
reason why we could not provide more alignment for some items in the
static store.  Seems to me like we could provide 8 byte alignment
for doubles, long doubles and arrays which have doubles or long
doubles as elements.

For at least the Fortran folks this would get most of their data
aligned on a suitable boundary to improve performance.

Note that we'd also want to look into aligning doubles and long
doubles in the constant pool!

Anyone want a nice little project to improve x86 performance? :-)

jeff

  reply	other threads:[~1998-02-22 18:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-22 16:39 Stan Cox
1998-02-22 18:48 ` Jeffrey A Law [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-07-10 13:32 John Wehle
1998-07-10 21:04 ` John Polstra
1998-07-11 22:54 ` Jeffrey A Law
1998-07-05 23:38 Jeffrey A Law
1998-02-08 22:42 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=6298.888202223@hurl.cygnus.com \
    --to=law@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=scox@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).