public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jamie Lokier <egcs@tantalophile.demon.co.uk>
To: Nix <nix@esperi.demon.co.uk>
Cc: Richard Henderson <rth@redhat.com>,
	"Davis, Bryan" <BRDavis@dsrnet.com>,
	gcc@gcc.gnu.org
Subject: Re: -malign-double switch patch?
Date: Sat, 10 Aug 2002 18:12:00 -0000	[thread overview]
Message-ID: <20020811021111.A1320@kushida.apsleyroad.org> (raw)
In-Reply-To: <87wuqzldxv.fsf@amaterasu.srvr.nix>

Nix wrote:
> > Apparently you didn't read the documentation, in which it is said
> > that the switch affects the abi, and therefore should be used only
> > with extreme caution under controled conditions.
> 
> GCC-3.1.x's manual says
> 
> ,----
> | `-malign-double'
> | `-mno-align-double'
> |      Control whether GCC aligns `double', `long double', and `long
> |      long' variables on a two word boundary or a one word boundary.
> |      Aligning `double' variables on a two word boundary will produce
> |      code that runs somewhat faster on a `Pentium' at the expense of
> |      more memory.
> `----
> 
> i.e., it doesn't mention the ABI breakage :( perhaps this is only in the
> trunk...

The next paragraph says:

     *Warning:* if you use the `-malign-double' switch, structures
     containing the above types will be aligned differently than the
     published application binary interface specifications for the 386.

Now, if you're not using structures, perhaps it isn't obvious that you
can still have ABI breakage...  (Argument alignment on the stack
changes, doesn't it?)

-- Jamie

  reply	other threads:[~2002-08-10 18:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-08 14:09 Davis, Bryan
2002-08-09 15:35 ` Richard Henderson
2002-08-09 18:32   ` Nix
2002-08-10 18:12     ` Jamie Lokier [this message]
2002-08-10 21:26       ` Ross Smith
2002-08-10 22:25         ` Richard Henderson
2002-08-11  6:58           ` Ross Smith
2002-08-11  7:36             ` Jamie Lokier
2002-08-10 22:24       ` Richard Henderson

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=20020811021111.A1320@kushida.apsleyroad.org \
    --to=egcs@tantalophile.demon.co.uk \
    --cc=BRDavis@dsrnet.com \
    --cc=gcc@gcc.gnu.org \
    --cc=nix@esperi.demon.co.uk \
    --cc=rth@redhat.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).