Hi,
According to commit log, this file is created in the year 2018, hence
the copyright year should be corrected to 2018.
Is below patch ok to fix this problem?
Thanks
Wei Xiao
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 62e32c6..416dbd1 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
Handle new march.
Wei Xiao 于2018年11月29日周四 下午4:32写道:
>
> Hi
>
> Distinguish based on stepping number is not recommended for some reasons:
> 1) Intel doesn't officially disclose stepping information in SDM.
> 2) Stepping can be changing in the future.
>
> We still prefer the
le cascadelake.
> > * config/i386/i386.h (TARGET_CASCADELAKE, PROCESSOR_CASCADELAKE): New.
> > (PTA_CASCADELAKE): Ditto.
> > * doc/invoke.texi: Add -march=cascadelake.
> >
> > gcc/testsuite/
> > * gcc.target/i386/funcspec-56.inc: Handle
Thanks for the comments!
Fixed as attached.
Ok for trunk?
Jakub Jelinek 于2018年12月14日周五 下午6:47写道:
>
> On Fri, Dec 14, 2018 at 06:33:37PM +0800, Wei Xiao wrote:
> --- a/gcc/config/i386/driver-i386.c
> +++ b/gcc/config/i386/driver-i386.c
> @@ -832,8 +832,16 @@ const char *host_detect
Hi,
The attached patch updates VFIXUPIMM* Intrinsics to align with the
latest Intel® 64 and IA-32 Architectures Software Developer’s Manual
(SDM).
Tested with GCC regression test on x86, no regression.
Is it ok?
Thanks
Wei
gcc/
2018-10-30 Wei Xiao
*config/i386/avx512fintrin.h
Hi Uros and HJ,
I have updated the patch according to your remarks as attached.
Ok for trunk?
Thanks
Wei
gcc/
2018-11-2 Wei Xiao
*config/i386/avx512fintrin.h: Update VFIXUPIMM* intrinsics.
(_mm512_fixupimm_round_pd): Update parameters and builtin
> Please also rename these:
>
> _mm512_mask_fixupimm_round_pd (__m512d __A, __mmask8 __U, __m512d __B,
> __m512i __C, const int __imm, const int __R)
>
> _mm512_mask_fixupimm_round_ps (__m512 __A, __mmask16 __U, __m512 __B,
> __m512i __C, const int __imm, c
Hi maintainers,
The attached patch intends to optimize VFIXUPIMM* patterns with
multiple-alternative constraints and
4 patterns are combined into 2 patterns. Tested with bootstrap and
regression tests on x86_64. No regressions.
Is it OK for trunk?
Thanks,
Wei
opt-vfixupimm-v1.diff
Description:
sure the new pattern
paradigm is ok for x86 maintainer through this patch.
Wei
Uros Bizjak 于2018年11月7日周三 下午3:24写道:
>
> On Tue, Nov 6, 2018 at 11:16 AM Wei Xiao wrote:
> >
> > Hi maintainers,
> >
> > The attached patch intends to optimize VFIXUPIMM* patterns with
> >
Hi,
The attached patch added -march=cascadelake for x86.
Tested with bootstrap and regression tests on x86_64. No regressions.
Is it ok for trunk?
Wei
gcc/
* common/config/i386/i386-common.c (processor_names): Add cascadelake.
(processor_alias_table): Add cascadelake.
/funcspec-56.inc" Ditto.
libgcc/
* config/i386/cpuinfo.h: Add INTEL_COREI7_CASCADELAKE.
Jakub Jelinek 于2018年11月21日周三 下午7:09写道:
>
> On Wed, Nov 21, 2018 at 06:23:41PM +0800, Wei Xiao wrote:
> > The attached patch added -march=cascadelake for x86.
> > Tested with b
Thanks for the helpful information!
But I'm still checking with hardware team about the
family/model/stepping numbers for Cascadelake which are not officially
disclosed by Intel (to my best knowledge).
Wei
Martin Liška 于2018年11月26日周一 下午10:00写道:
>
> On 11/26/18 12:18 PM, Jakub Jelinek wrote:
> > O
march.
* gcc.target/i386/builtin_target.c: Ditto.
* gcc.target/i386/funcspec-56.inc: Ditto.
libgcc/
* config/i386/cpuinfo.c (get_intel_cpu): Handle cascadelake.
* config/i386/cpuinfo.h: Add INTEL_COREI7_CASCADELAKE.
Wei Xiao 于2018年11月27日周二 下午6:40写道:
>
> Thanks for
Hi,
It turns out that the Intel 64 and IA-32 Architectures Software Developer
Manuals (SDM) description about the fixupimm intrinsic is incorrect. So we need
to revert 3 patches related to it: r265827, r266026 and r267160.
Sorry for the inconvenience.
Is it ok?
Wei
elinek 于2019年1月15日周二 下午11:20写道:
>
> On Tue, Jan 15, 2019 at 04:14:06PM +0100, Uros Bizjak wrote:
> > On Tue, Jan 15, 2019 at 3:40 PM Wei Xiao wrote:
> > >
> > > Hi,
> > >
> > > It turns out that the Intel 64 and IA-32 Architectures Software Develope
The original runtime testcases are incorrect and I have fixed them as attached.
Is it ok to do the revert and fix the testcases for trunk?
Wei
2019-01-16 Wei Xiao
* gcc.target/i386/avx512f-vfixupimmpd-2.c: Fix the test cases for
VFIXUPIMM* intrinsics.
* gcc.target
> > > For r267160, I'd expect you want to revert just the config/i386/ part and
> > > keep the testcases, they should work even with the changes reverted,
> > > right?
> > >
> > The testcase part also need to be reverted since we have changed them
> > according to the incorrect intrinsic list in S
17 matches
Mail list logo