www.delorie.com/archives/browse.cgi   search  
Mail Archives: pgcc/2000/02/03/10:07:00

Date: Thu, 3 Feb 2000 13:11:54 +0100
From: Jan Hubicka <hubicka AT atrey DOT karlin DOT mff DOT cuni DOT cz>
To: pgcc AT delorie DOT com
Subject: Re: pgcc and egcs alignment -- function, basic block and string
Message-ID: <20000203131154.C12247@atrey.karlin.mff.cuni.cz>
References: <38921CD6 DOT 2A725779 AT ix DOT netcom DOT com> <20000129032101 DOT A25630 AT atrey DOT karlin DOT mff DOT cuni DOT cz> <38940264 DOT 30C35BDD AT neuss DOT netsurf DOT de> <20000130211158 DOT D641 AT cerebro DOT laendle> <38988672 DOT B47AFFD8 AT ix DOT netcom DOT com>
Mime-Version: 1.0
X-Mailer: Mutt 1.0i
In-Reply-To: <38988672.B47AFFD8@ix.netcom.com>; from cbsears@ix.netcom.com on Wed, Feb 02, 2000 at 11:33:06AM -0800
Reply-To: pgcc AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: pgcc AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

> 
> As far as aligning strings goes, it appears that egcs 2.95.2
> doesn't align strings at all.  I would have preferred long word
> alignment, and I would have preferred a command line option,
> but I can live with this.  (As opposed to cacheline alignment
> of strings.)
I believe that default scheme is to align only strings longer than
the alignment itself.
So only strings longer than 32 bytes gets aligned (to 32 bytes).

Honza

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019