Date: Thu, 1 Jun 2000 16:28:04 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Gisle Vanem <giva AT bgnett DOT no>
cc: djgpp AT delorie DOT com
Subject: Re: Inline asm: lcall & various binutils versions
In-Reply-To: <Pine.UW2.3.95.1000601145005.25970A-100000@bryggen.bgnett.no>
Message-ID: <Pine.SUN.3.91.1000601162452.20285F-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Thu, 1 Jun 2000, Gisle Vanem wrote:

> First 32-bit must be a linear offset and immediatially followed by 16-bit
> for a valid selector (bigendian layout).  If gcc should optimise and align
> '__dpmi_paddr.selector' differently it would no longer be a valid selector
> at that address.

I don't think GCC currently makes such opimizations, does it?  16-bit 
values should be aligned on a word boundary, so there should be no
reason for GCC not to lay out __dpmi_paddr as you say it should be.

> What's wrong with #pragma's anyway?

They tend to change too much with compiler versions.  The `pack' pragma, 
in particular, has a bad record of breaking DJGPP, especially in C++ 
programs.