Re: Use of vector instructions in memmov/memset expanding

[Michael Zolotukhin <michael dot v dot zolotukhin at gmail dot com>]

And here is a fixed version of back-end patch.

On 29 September 2011 15:15, Michael Zolotukhin
<michael.v.zolotukhin@gmail.com> wrote:
> Here is a fixed version of middle-end patch.
>
> On 29 September 2011 15:14, Michael Zolotukhin
> <michael.v.zolotukhin@gmail.com> wrote:
>>>> Michael,
>>>> ? ?Did you bootstrap with --enable-checking=yes? I am seeing the bootstrap
>>>> failure...
>>> I checked bootstrap, specs and 'make check' with the complete patch.
>>> Separate patches for ME and BE were only tested for build (no
>>> bootstrap) and 'make check'. I think it's better to apply the complete
>>> patch, but review the separate patches (to make it easier).
>>
>> I rechecked bootstrap, and it failed.. Seemingly, something went wrong
>> when I updated my branches, but I've already fixed it.
>>
>> Here is fixed version of complete patch.
>>
>> On 29 September 2011 09:39, Michael Zolotukhin
>> <michael.v.zolotukhin@gmail.com> wrote:
>>>> Michael,
>>>> ? ?Did you bootstrap with --enable-checking=yes? I am seeing the bootstrap
>>>> failure...
>>> I checked bootstrap, specs and 'make check' with the complete patch.
>>> Separate patches for ME and BE were only tested for build (no
>>> bootstrap) and 'make check'. I think it's better to apply the complete
>>> patch, but review the separate patches (to make it easier).
>>>
>>>> ps There also seems to be common sections in the memfunc-mid.patch and memfunc-be.patch patches.
>>> That's true, some new routines from middle-end are used in back-end
>>> changes - I couldn't separate the patches in other way without
>>> significant changes in them.
>>>
>>>
>>> On 29 September 2011 01:51, Jack Howarth <howarth@bromo.med.uc.edu> wrote:
>>>> On Wed, Sep 28, 2011 at 05:33:23PM +0400, Michael Zolotukhin wrote:
>>>>> > ? It appears that part 1 of the patch wasn't really attached.
>>>>> Thanks, resending.
>>>>
>>>> Michael,
>>>> ? ?Did you bootstrap with --enable-checking=yes? I am seeing the bootstrap
>>>> failure...
>>>>
>>>> /sw/src/fink.build/gcc47-4.7.0-1/darwin_objdir/./prev-gcc/g++ -B/sw/src/fink.build/gcc47-4.7.0-1/darwin_objdir/./prev-gcc/ -B/sw/lib/gcc4.7/x86_64-apple-darwin11.2.0/bin/ -nostdinc++ -B/sw/src/fink.build/gcc47-4.7.0-1/darwin_objdir/prev-x86_64-apple-darwin11.2.0/libstdc++-v3/src/.libs -B/sw/src/fink.build/gcc47-4.7.0-1/darwin_objdir/prev-x86_64-apple-darwin11.2.0/libstdc++-v3/libsupc++/.libs -I/sw/src/fink.build/gcc47-4.7.0-1/darwin_objdir/prev-x86_64-apple-darwin11.2.0/libstdc++-v3/include/x86_64-apple-darwin11.2.0 -I/sw/src/fink.build/gcc47-4.7.0-1/darwin_objdir/prev-x86_64-apple-darwin11.2.0/libstdc++-v3/include -I/sw/src/fink.build/gcc47-4.7.0-1/gcc-4.7-20110927/libstdc++-v3/libsupc++ -L/sw/src/fink.build/gcc47-4.7.0-1/darwin_objdir/prev-x86_64-apple-darwin11.2.0/libstdc++-v3/src/.libs -L/sw/src/fink.build/gcc47-4.7.0-1/darwin_objdir/prev-x86_64-apple-darwin11.2.0/libstdc++-v3/libsupc++/.libs -c ? -g -O2 -mdynamic-no-pic -gtoggle -DIN_GCC ? -W -Wall -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Werror -fno-common ?-DHAVE_CONFIG_H -I. -I. -I../../gcc-4.7-20110927/gcc -I../../gcc-4.7-20110927/gcc/. -I../../gcc-4.7-20110927/gcc/../include -I../../gcc-4.7-20110927/gcc/../libcpp/include -I/sw/include -I/sw/include ?-I../../gcc-4.7-20110927/gcc/../libdecnumber -I../../gcc-4.7-20110927/gcc/../libdecnumber/dpd -I../libdecnumber -I/sw/include ?-I/sw/include -DCLOOG_INT_GMP -DCLOOG_ORG -I/sw/include ../../gcc-4.7-20110927/gcc/emit-rtl.c -o emit-rtl.o
>>>> ../../gcc-4.7-20110927/gcc/emit-rtl.c: In function ‘rtx_def* adjust_address_1(rtx, machine_mode, long int, int, int)’:
>>>> ../../gcc-4.7-20110927/gcc/emit-rtl.c:2060:26: error: unused variable ‘max_align’ [-Werror=unused-variable]
>>>> cc1plus: all warnings being treated as errors
>>>>
>>>> on x86_64-apple-darwin11 with your patches.
>>>> ? ? ? ? ?Jack
>>>> ps There also seems to be common sections in the memfunc-mid.patch and memfunc-be.patch patches.
>>>>
>>>
>>>
>>>
>>> --
>>> ---
>>> Best regards,
>>> Michael V. Zolotukhin,
>>> Software Engineer
>>> Intel Corporation.
>>>
>>
>>
>>
>> --
>> ---
>> Best regards,
>> Michael V. Zolotukhin,
>> Software Engineer
>> Intel Corporation.
>>
>
>
>
> --
> ---
> Best regards,
> Michael V. Zolotukhin,
> Software Engineer
> Intel Corporation.
>



-- 
---
Best regards,
Michael V. Zolotukhin,
Software Engineer
Intel Corporation.

Attachment: memfunc-be-2.patch
Description: Binary data