Sender: root AT delorie DOT com
Message-ID: <377BB217.2FFBAEA8@inti.gov.ar>
Date: Thu, 01 Jul 1999 15:23:19 -0300
From: salvador <salvador AT inti DOT gov DOT ar>
Organization: INTI
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686)
X-Accept-Language: es-AR, en, es
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
CC: Robert Hoehne <robert DOT hoehne AT gmx DOT net>, Eric Rudd <rudd AT cyberoptics DOT com>
Subject: Re: .align directives in libc.a
References: <Pine DOT SUN DOT 3 DOT 91 DOT 990701074005 DOT 22046A-100000 AT is>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Eli Zaretskii wrote:

> I see that the behavior of `.align' in Binutils 2.9.1 has changed for
> coff-go32 targets: ".align N" is now the same as ".p2align N", whereas
> in 2.8.1 and before it worked like ".balign N".  This probably means
> that we need to change library sources, but how?  What code alignment
> do we want, and with what value should we instruct the Gas to pad?

Can we tell Gas to use "int 3" (or other trap) when pading between functions?
(and any other place where the code should never be executed).

> Intel manuals seem to recommend 16-byte alignment, both for code and
> for data.

And that's normally the best. MSVC uses 16 and 32 (based on some strange
criteria).
But looks like the most sensitive stuff is the entry point of functions, not the
align of loops or jumps.

SET

--
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Visit my home page: http://welcome.to/SetSoft or
http://www.geocities.com/SiliconValley/Vista/6552/
Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org
                    set AT ieee DOT org set-soft AT bigfoot DOT com
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA Phone: +(5411) 4759 0013