Message-ID: <19990722071323.20692.qmail@daffy.airs.com>
Date: 22 Jul 1999 03:13:23 -0400
From: Ian Lance Taylor <ian AT zembu DOT com>
To: donn AT verinet DOT com
CC: snowball3 AT bigfoot DOT com, binutils AT sourceware DOT cygnus DOT com,
        djgpp-workers AT delorie DOT com
In-reply-to: <37968ECF.E35A6119@verinet.com> (message from Donn Terry on Wed,
	21 Jul 1999 21:23:59 -0600)
Subject: Re: DJGPP and alignment
References: <199907211607 DOT QAA38452 AT out1 DOT ibm DOT net>; from Mark E. on Wed, Jul 21, 1999 at 12:07:18PM -0400 <199907220030 DOT AAA09334 AT out5 DOT ibm DOT net> <19990722003428 DOT 12362 DOT qmail AT daffy DOT airs DOT com> <37968ECF DOT E35A6119 AT verinet DOT com>
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

   Date: Wed, 21 Jul 1999 21:23:59 -0600
   From: Donn Terry <donn AT verinet DOT com>

   In the case of .ctors and .dtors, I think Ian is
   right to characterize
   the zeros as "unsightly".  For  .idata and .pdata, they're catastrophic.

Just for the record, I was being facetious.  Zeroes are also
catastrophic in .ctors and .dtors.  The code in gcc's crtbegin file
will call each address in the .ctors section.  If there is a zero
there, it will wind up jumping to the zero address.

Ian