Re: generated movaps with unaligned memory

2009-02-24 Thread Jiri Olsa
On Tue, Feb 24, 2009 at 3:53 PM, H.J. Lu wrote: > On Mon, Feb 23, 2009 at 11:46 PM, Jiri Olsa wrote: >> On Mon, Feb 23, 2009 at 7:48 PM, H.J. Lu wrote: >>> On Mon, Feb 23, 2009 at 10:39 AM, Jiri Olsa wrote: On Mon, Feb 23, 2009 at 7:35 PM, H.J. Lu wrote: > On Mon, Feb 23, 2009 at 10:0

Re: generated movaps with unaligned memory

2009-02-24 Thread H.J. Lu
On Mon, Feb 23, 2009 at 11:46 PM, Jiri Olsa wrote: > On Mon, Feb 23, 2009 at 7:48 PM, H.J. Lu wrote: >> On Mon, Feb 23, 2009 at 10:39 AM, Jiri Olsa wrote: >>> On Mon, Feb 23, 2009 at 7:35 PM, H.J. Lu wrote: On Mon, Feb 23, 2009 at 10:05 AM, Jiri Olsa wrote: > Hi, > > my shared

Re: generated movaps with unaligned memory

2009-02-23 Thread Jiri Olsa
On Mon, Feb 23, 2009 at 7:48 PM, H.J. Lu wrote: > On Mon, Feb 23, 2009 at 10:39 AM, Jiri Olsa wrote: >> On Mon, Feb 23, 2009 at 7:35 PM, H.J. Lu wrote: >>> On Mon, Feb 23, 2009 at 10:05 AM, Jiri Olsa wrote: Hi, my shared library crashes with movaps instruction using not aligned m

Re: generated movaps with unaligned memory

2009-02-23 Thread H.J. Lu
On Mon, Feb 23, 2009 at 10:39 AM, Jiri Olsa wrote: > On Mon, Feb 23, 2009 at 7:35 PM, H.J. Lu wrote: >> On Mon, Feb 23, 2009 at 10:05 AM, Jiri Olsa wrote: >>> Hi, >>> >>> my shared library crashes with movaps instruction using not aligned memory. >>> >>> Since the shared library function is bein

Re: generated movaps with unaligned memory

2009-02-23 Thread Jiri Olsa
On Mon, Feb 23, 2009 at 7:35 PM, H.J. Lu wrote: > On Mon, Feb 23, 2009 at 10:05 AM, Jiri Olsa wrote: >> Hi, >> >> my shared library crashes with movaps instruction using not aligned memory. >> >> Since the shared library function is being called from dynamic linker, which >> basically prepares th

Re: generated movaps with unaligned memory

2009-02-23 Thread H.J. Lu
On Mon, Feb 23, 2009 at 10:05 AM, Jiri Olsa wrote: > Hi, > > my shared library crashes with movaps instruction using not aligned memory. > > Since the shared library function is being called from dynamic linker, which > basically prepares the memory location, I'm not sure whoose side issues this