Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Dave Korn" <dk AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: g++ 3.4.0 cygwin, codegen SSE & alignement issues
Date: Thu, 29 Apr 2004 11:23:17 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <409094D4.5070202@ompf.org>
Message-ID: <NUTMEGyhzIMStZuhyx4000000b2@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime: 29 Apr 2004 10:23:17.0968 (UTC) FILETIME=[FD074D00:01C42DD3]

> -----Original Message-----
> From: cygwin-owner On Behalf Of tbp
> Sent: 29 April 2004 06:38

> That will surely do wonders for the stack alignement issue, 
> but there's 
> another fold that i'm still unsure how to handle. Under some 
> circumstances some *ps instructions are generated touching non local 
> memory (put in .rdata with 4 byte alignement as pointed out 
> by Ross Ridge):
> objdump ...|grep ...
>    404264:       xorps  0x43af84,%xmm4
>    4062a7:       xorps  0x43b304,%xmm2
>    40872a:       xorps  0x43b33c,%xmm2
>    40ab83:       andps  0x43b8ec,%xmm0
>    40c5ab:       xorps  0x43bbb0,%xmm0
>    41dc47:       xorps  0x444358,%xmm2
>    42b006:       xorps  0x43ad94,%xmm1
> 
> I guess i could try to track those constants and put them in 
> their own 
> section or something, but is there a proper fix in the work 
> by someone 
> knowledgeable?

Not a fix, but a workaround:  specify them all explicitly as const vector
int variables (initialised to the relevant value), then you can use the
__attribute__ ((aligned (...))) syntax.


    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/