[macstl-dev] Re: -faltivec without -maltivec copying; gcc's altivec attributes

[Glen Low]

On 04/08/2005, at 11:09 PM, Ilya Lipovsky wrote:

> Hi Glen,
> I get memcpy() in the prologue codes, as well. It, actually, copies  
> elements from one area of the stack into another one. Usually it  
> copies less than 100 bytes. I, too, tried to get rid off it, but  
> couldn't.
>
> -Ilya

Do you get it with some kinds of expressions only? I managed to  
suppress it by declaring the obvious copy constructor for  
literal_iterator, for an expression involving literals, and by  
changing the

union_type un = {v0};

to

union_type un;
un.val [0] = v0;

etc.

Apparently the former calls a copy constructor.

The changes will be in the next Subversion commit (one or two day's  
time).


Cheers, Glen Low


---
pixelglow software | simply brilliant stuff
www.pixelglow.com
aim: pixglen

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pixelglow.com/lists/archive/macstl-dev/attachments/20050805/ad78e657/attachment.html