On Tue, Nov 12, 2019 at 11:35 AM Hongtao Liu <crazy...@gmail.com> wrote: > > Hi: > As mentioned in https://gcc.gnu.org/ml/gcc-patches/2019-11/msg00832.html > > So yes, it's poorly named. A preparatory patch to clean this up > > (and maybe split it into TARGET_AVX256_SPLIT_REGS and TARGET_AVX128_OPTIMAL) > > would be nice. > > Bootstrap and regression test for i386 backend is ok. > Ok for trunk?
It looks OK to me, please let x86 maintainers a day to comment, otherwise OK. Thanks, Richard. > Changelog > gcc/ > PR target/92448 > * config/i386/i386-expand.c (ix86_expand_set_or_cpymem): > Replace TARGET_AVX128_OPTIMAL with TARGET_AVX256_SPLIT_REGS. > * config/i386/i386-option.c (ix86_vec_cost): Ditto. > (ix86_reassociation_width): Ditto. > * config/i386/i386-options.c (ix86_option_override_internal): > Replace TARGET_AVX128_OPTIAML with > ix86_tune_features[X86_TUNE_AVX128_OPTIMAL] > * config/i386/i386.h (TARGET_AVX256_SPLIT_REGS): New macro. > (TARGET_AVX128_OPTIMAL): Deleted. > * config/i386/x86-tune.def (X86_TUNE_AVX256_SPLIT_REGS): New > DEF_TUNE. > > -- > BR, > Hongtao
