[AVX]: More AVX updates

[H.J. Lu]

I have to use

return "%v0movaps\t{%1, %0|%0, %1}";

since it asks for a operand number even if isn't needed. I don't like
this unused operand number. Also it doesn't work on cases where
AVX needs one more operand.

H.J.
On Fri, May 23, 2008 at 1:45 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
> Hi Uros,
>
> It sounds a good idea. I will give it a try.
>
> Thanks.
>
>
> H.J.
> On Fri, May 23, 2008 at 1:27 PM, Uros Bizjak <ubizjak@gmail.com> wrote:
>> Hello!
>>
>>> I am checking this patch into AVX branch. Now we can generate
>>> pure AVX codes for all intrinsics in 64bit.
>>>  -  "cvtts<ssemodefsuffix>2si\t{%1, %0|%0, %1}"
>>> +  "* return TARGET_AVX +            ? \"vcvtts<ssemodefsuffix>2si\t{%1,
>>> %0|%0, %1}\"
>>> +            :\"cvtts<ssemodefsuffix>2si\t{%1, %0|%0, %1}\";"
>>>
>>
>> What do you think about adding "%v" asm directive, i.e.:
>>
>> "%vcvtts<ssemodefsuffix>2si\t{%1, %0|%0, %1}"
>>
>> and output 'v' in print_operand () function, depending on TARGET_AVX? This
>> would simplify a lot of insn templates, probably even more when 'enabled'
>> attribute is used.
>>
>> Uros.
>>
>