[PATCH] Expand __builtin_memcmp_eq with ptest for OImode.

This is adjusted patch only for OImode. Bootstrapped and regtested on x86_64-pc-linux-gnu{-m32,}. Ok for trunk? gcc/ChangeLog: PR target/104610 * config/i386/i386-expand.cc (ix86_expand_branch): Use ptest for QImode when code is EQ or NE. * config/i386/sse.md (cbr

Re: [PATCH] PR105169 Fix references to discarded sections

Hi, On Tue, 2022-04-19 at 10:11 +0200, Richard Biener wrote: > On Thu, 14 Apr 2022, Giuliano Belinassi wrote: > > > When -fpatchable-function-entry= is enabled, certain C++ codes > > fails to > > link because of generated references to discarded sections in > > __patchable_function_entry section.

RE: [PATCH] [i386]Add combine splitter to transform pxor/pcmpeqb/pmovmskb/cmp 0xffff to ptest.

> -Original Message- > From: Uros Bizjak > Sent: Friday, May 6, 2022 4:59 PM > To: Jiang, Haochen > Cc: gcc-patches@gcc.gnu.org; Liu, Hongtao > Subject: Re: [PATCH] [i386]Add combine splitter to transform > pxor/pcmpeqb/pmovmskb/cmp 0x to ptest. > > On Fri, May 6, 2022 at 10:01 AM

RE: [PATCH] [i386]Add combine splitter to transform pxor/pcmpeqb/pmovmskb/cmp 0xffff to ptest.

> -Original Message- > From: Hongyu Wang > Sent: Friday, May 6, 2022 4:50 PM > To: Jiang, Haochen > Cc: GCC Patches ; Liu, Hongtao > > Subject: Re: [PATCH] [i386]Add combine splitter to transform > pxor/pcmpeqb/pmovmskb/cmp 0x to ptest. > > > +(define_split > > + [(set (reg:CCZ FLA

RE: [PATCH] Reconstruct i386 testsuite with __builtin_cpu_supports

Hi Uros, I understand that we always keep the old testcases there. It is always safe to do that. But I have another question, if we add something new in one of the existing files in the future, should we use __builtin_cpu_supports to keep the code clearer or stick to cpuids? I believe __built

Go patch committed: Remove Array_index_expression::is_lvalue_

This patch to the Go fronend removes the is_lvalue_ field from Array_index_expression. As of https://go.dev/cl/77510 (https://gcc.gnu.org/pipermail/gcc-patches/2017-November/487697.html) it is never used. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed to mainline. Ian 55e0e

[committed 1/2] libstdc++: Fix deserialization for std::normal_distribution [PR105502]

Tested powerpc64le-linux, pushed to trunk. Backports to all branches needed. -- >8 -- This fixes a regression in std::normal_distribution deserialization that caused the object to be left unchanged if the __state_avail value read from the stream was false. libstdc++-v3/ChangeLog: PR lib

[committed 2/2] libstdc++: Simplify std::normal_distribution equality operator

Tested powerpc64le-linux, pushed to trunk. -- >8 -- libstdc++-v3/ChangeLog: * include/bits/random.tcc (operator==): Only check normal_distribution::_M_saved_available once. * testsuite/26_numerics/random/normal_distribution/operators/equal.cc: Check equality after

Re: [ping2][PATCH 0/8][RFC] Support BTF decl_tag and type_tag annotations

On 5/5/22 16:00, Yonghong Song wrote: On 5/4/22 10:03 AM, David Faust wrote: On 5/3/22 15:32, Joseph Myers wrote: On Mon, 2 May 2022, David Faust via Gcc-patches wrote: Consider the following example:     #define __typetag1 __attribute__((btf_type_tag("tag1")))     #define __typetag

Re: [PATCH] c++: constexpr init of union sub-aggr w/ base [PR105491]

On Fri, 6 May 2022, Jason Merrill wrote: > On 5/6/22 16:10, Patrick Palka wrote: > > On Fri, 6 May 2022, Patrick Palka wrote: > > > > > On Fri, 6 May 2022, Jason Merrill wrote: > > > > > > > On 5/6/22 14:00, Patrick Palka wrote: > > > > > On Fri, 6 May 2022, Patrick Palka wrote: > > > > > > > >

[PATCH] Guard against applying scale with 0 denominator

Calling count.apply_scale with a 0 denominator causes an assert. This change guards against that. Tested on x86_64-pc-linux-gnu. gcc/ChangeLog: * tree-loop-vect-manip.cc (vect_do_peeling): Guard against applying scale with 0 denominator. --- gcc/tree-vect-loop-manip.cc | 9 + 1

[pushed] c++: empty base constexpr adjustment [PR105245]

While looking at PR105245 in stage 4, I wanted to reorganize the code a bit, but it seemed prudent to defer that to stage 1. Tested x86_64-pc-linux-gnu, applying to trunk. PR c++/105245 PR c++/100111 gcc/cp/ChangeLog: * constexpr.cc (cxx_eval_store_expression): Reorganiz

Re: [PATCH] c++: constexpr init of union sub-aggr w/ base [PR105491]

On 5/6/22 16:10, Patrick Palka wrote: On Fri, 6 May 2022, Patrick Palka wrote: On Fri, 6 May 2022, Jason Merrill wrote: On 5/6/22 14:00, Patrick Palka wrote: On Fri, 6 May 2022, Patrick Palka wrote: On Fri, 6 May 2022, Jason Merrill wrote: On 5/6/22 11:22, Patrick Palka wrote: Here ever

Re: [PATCH] c++: constexpr init of union sub-aggr w/ base [PR105491]

On Fri, 6 May 2022, Patrick Palka wrote: > On Fri, 6 May 2022, Jason Merrill wrote: > > > On 5/6/22 14:00, Patrick Palka wrote: > > > On Fri, 6 May 2022, Patrick Palka wrote: > > > > > > > On Fri, 6 May 2022, Jason Merrill wrote: > > > > > > > > > On 5/6/22 11:22, Patrick Palka wrote: > > > > >

Re: [PATCH] c++: constexpr init of union sub-aggr w/ base [PR105491]

On Fri, 6 May 2022, Jason Merrill wrote: > On 5/6/22 14:00, Patrick Palka wrote: > > On Fri, 6 May 2022, Patrick Palka wrote: > > > > > On Fri, 6 May 2022, Jason Merrill wrote: > > > > > > > On 5/6/22 11:22, Patrick Palka wrote: > > > > > Here ever since r10-7313-gb599bf9d6d1e18, > > > > > reduc

Re: [PATCH v3] libstdc++: ppc: conditionalize vsx-only simd intrinsics

On May 6, 2022, Jonathan Wakely wrote: > On Fri, 6 May 2022 at 17:17, Segher Boessenkool wrote: >> > +#if defined __VSX__ || __LONG_WIDTH__ == 32 >> > _GLIBCXX_SIMD_PPC_INTRIN(signed long); >> > _GLIBCXX_SIMD_PPC_INTRIN(unsigned long); >> > +#endif >> >> Is __LONG_WIDTH__ the right macro to u

Re: [PATCH] c++: constexpr init of union sub-aggr w/ base [PR105491]

On 5/6/22 14:00, Patrick Palka wrote: On Fri, 6 May 2022, Patrick Palka wrote: On Fri, 6 May 2022, Jason Merrill wrote: On 5/6/22 11:22, Patrick Palka wrote: Here ever since r10-7313-gb599bf9d6d1e18, reduced_constant_expression_p in C++11/14 is rejecting the marked sub-aggregate initializer

Go patch committed: Reject duplicate bool keys in a map literal

This patch to the Go frontend rejects duplicate bool keys in a map literal. This is hardly a common case, but we may as well get it right. This is for https://go.dev/issue/35945 and htps://go.dev/issue/28104. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed to mainline. Ian

Re: [PATCH] [PR100106] Reject unaligned subregs when strict alignment is required

On 2022-05-05 02:52, Alexandre Oliva wrote: Regstrapped on x86_64-linux-gnu and ppc64le-linux-gnu, also tested targeting ppc- and ppc64-vx7r2. Ok to install? I am ok with the modified version of the patch.  It looks reasonable for me and I support its commit. But I think I can not approve

Re: [PATCH] c++: constexpr init of union sub-aggr w/ base [PR105491]

On Fri, 6 May 2022, Patrick Palka wrote: > On Fri, 6 May 2022, Jason Merrill wrote: > > > On 5/6/22 11:22, Patrick Palka wrote: > > > Here ever since r10-7313-gb599bf9d6d1e18, reduced_constant_expression_p > > > in C++11/14 is rejecting the marked sub-aggregate initializer (of type S) > > > > >

Re: [PATCH v2] libstdc++: ppc: conditionalize vsx-only simd intrinsics

On Fri, 6 May 2022 at 17:17, Segher Boessenkool wrote: > > +#if defined __VSX__ || __LONG_WIDTH__ == 32 > > _GLIBCXX_SIMD_PPC_INTRIN(signed long); > > _GLIBCXX_SIMD_PPC_INTRIN(unsigned long); > > +#endif > > Is __LONG_WIDTH__ the right macro to use here? Nothing else in > libstdc++v3 uses it. "

Re: Ping #5: [PATCH, V4] Eliminate power8 fusion options, use power8 tuning, PR target/102059

On 5/5/22 4:27 PM, Segher Boessenkool wrote: > On Thu, May 05, 2022 at 02:59:07PM -0500, Peter Bergner wrote: >> On 5/5/22 2:35 PM, Segher Boessenkool wrote: >>> Just an unconditional >>> >>> callee_isa &= ~OPTION_MASK_P8_FUSION; >>> explicit_isa &= ~OPTION_MASK_P8_FUSION; >>> >>> will do, no?

Re: [patch][gcc13][i386][pr101891]Adjust -fzero-call-used-regs to always use XOR

> On May 6, 2022, at 10:58 AM, Uros Bizjak wrote: > > On Fri, May 6, 2022 at 4:29 PM Qing Zhao wrote: >> >> Hi, >> >> As Kee’s requested in this PR: >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101891 >> >> = >> >> Currently -fzero-call-used-regs will use a pattern of: >> >> XOR r

Re: [PATCH] c++: constexpr init of union sub-aggr w/ base [PR105491]

On Fri, 6 May 2022, Jason Merrill wrote: > On 5/6/22 11:22, Patrick Palka wrote: > > Here ever since r10-7313-gb599bf9d6d1e18, reduced_constant_expression_p > > in C++11/14 is rejecting the marked sub-aggregate initializer (of type S) > > > >W w = {.D.2445={.s={.D.2387={.m=0}, .b=0}}} > >

Re: [PATCH, OpenMP] Implement uses_allocators clause for target regions

Hi Chung-Lin, thanks for the patch – and some comments from my side. On 06.05.22 15:20, Chung-Lin Tang wrote: For user defined allocator handles, this allows target regions to assign memory space and traits to allocators, and automatically calls omp_init/destroy_allocator() in the beginning/end

Re: [PATCH v2] libstdc++: ppc: conditionalize vsx-only simd intrinsics

On Mon, May 02, 2022 at 11:00:02PM -0300, Alexandre Oliva wrote: > On May 2, 2022, Segher Boessenkool wrote: > > Send full patches always please. > > I'll try to remember that. In case I fail, I hope you won't mind too > much reminding me. > > (You'd also asked me not to send patches as follow

Re: [PATCH] c++: constexpr init of union sub-aggr w/ base [PR105491]

On Fri, May 06, 2022 at 11:56:30AM -0400, Jason Merrill via Gcc-patches wrote: > On 5/6/22 11:22, Patrick Palka wrote: > > Here ever since r10-7313-gb599bf9d6d1e18, reduced_constant_expression_p > > in C++11/14 is rejecting the marked sub-aggregate initializer (of type S) > > > >W w = {.D.2445

Re: [patch][gcc13][i386][pr101891]Adjust -fzero-call-used-regs to always use XOR

On Fri, May 6, 2022 at 4:29 PM Qing Zhao wrote: > > Hi, > > As Kee’s requested in this PR: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101891 > > = > > Currently -fzero-call-used-regs will use a pattern of: > > XOR regA,regA > MOV regA,regB > MOV regA,regC > ... > RET > > However, this int

Re: [PATCH] c++: constexpr init of union sub-aggr w/ base [PR105491]

On 5/6/22 11:22, Patrick Palka wrote: Here ever since r10-7313-gb599bf9d6d1e18, reduced_constant_expression_p in C++11/14 is rejecting the marked sub-aggregate initializer (of type S) W w = {.D.2445={.s={.D.2387={.m=0}, .b=0}}} ^ ultimately because said initializer has

[PATCH v2] Enable match.pd dumping with -fdump-tree-original

This is a respin of: https://gcc.gnu.org/pipermail/gcc-patches/2022-March/592307.html that implements Richard's suggestion around the cgraph.cc change. Otherwise the patch is as before. Bootstrapped and regtested on aarch64-linux-gnu, OK for trunk? Thanks, Alex -- I noticed that, while the

RE: [PATCH] aarch64: remove useless GPF_TF_F16 iterator

> -Original Message- > From: Gcc-patches bounces+kyrylo.tkachov=arm@gcc.gnu.org> On Behalf Of Christophe > Lyon via Gcc-patches > Sent: Friday, May 6, 2022 4:19 PM > To: gcc-patches@gcc.gnu.org > Subject: [PATCH] aarch64: remove useless GPF_TF_F16 iterator > > This iterator is not

[PATCH] c++: constexpr init of union sub-aggr w/ base [PR105491]

Here ever since r10-7313-gb599bf9d6d1e18, reduced_constant_expression_p in C++11/14 is rejecting the marked sub-aggregate initializer (of type S) W w = {.D.2445={.s={.D.2387={.m=0}, .b=0}}} ^ ultimately because said initializer has CONSTRUCTOR_NO_CLEARING set, and so the fu

[PATCH] aarch64: remove useless GPF_TF_F16 iterator

This iterator is not used anymore and is a leftover from previous cleanup (r10-5890-gabbe1ed2735517). 2022-04-28 Christophe Lyon gcc/ * config/aarch64/iterators.md (GPF_TF_F16): Delete. --- gcc/config/aarch64/iterators.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/g

Re: [PATCH] x86: Add missing .note.GNU-stack to assembly source

Hi H.J, > On Mon, May 2, 2022 at 11:37 AM H.J. Lu wrote: >> >> On Fri, Apr 29, 2022 at 10:38 AM H.J. Lu wrote: >> > >> > Add .note.GNU-stack assembly source to avoid linker warning: >> > >> > ld: warning: /tmp/ccPZSZ7Z.o: missing .note.GNU-stack section implies >> > executable stack >> > ld: NO

Re: [PATCH] lto-plugin: add support for feature detection

On Thu, 5 May 2022, Martin Liška wrote: > On 5/5/22 12:52, Alexander Monakov wrote: > > Feels a bit weird to ask, but before entertaining such an API extension, > > can we step back and understand the v3 variant of get_symbols? It is not > > documented, and from what little I saw I did not get

Re: [PATCH] x86: Add missing .note.GNU-stack to assembly source

On Mon, May 2, 2022 at 11:37 AM H.J. Lu wrote: > > On Fri, Apr 29, 2022 at 10:38 AM H.J. Lu wrote: > > > > Add .note.GNU-stack assembly source to avoid linker warning: > > > > ld: warning: /tmp/ccPZSZ7Z.o: missing .note.GNU-stack section implies > > executable stack > > ld: NOTE: This behaviour

Re: [PATCH] libsanitizer: cherry-pick commit b226894d475b from upstream

On Thu, May 5, 2022 at 2:02 PM H.J. Lu wrote: > > cherry-pick: > > b226894d475b [sanitizer] [sanitizer] Correct GetTls for x32 > --- > libsanitizer/sanitizer_common/sanitizer_linux_libcdep.cpp | 4 > 1 file changed, 4 insertions(+) > > diff --git a/libsanitizer/sanitizer_common/sanitizer_lin

[patch][gcc13][i386][pr101891]Adjust -fzero-call-used-regs to always use XOR

Hi, As Kee’s requested in this PR: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101891 = Currently -fzero-call-used-regs will use a pattern of: XOR regA,regA MOV regA,regB MOV regA,regC ... RET However, this introduces both a register ordering dependency (e.g. the CPU cannot clear regB w

[committed] libstdc++: Fix test that fails on Solaris [PR104731]

On Solaris the dirent::d_name member is a single char, causing this test to fail with warnings about buffer overflow. Change the test to use a union with additional space for writing a string to the d_name member. libstdc++-v3/ChangeLog: PR libstdc++/104731 * testsuite/27_io/files

[committed] libstdc++: Do not include in

Tested powerpc64le-linux, pushed to trunk. -- >8 -- This avoids polluting the global namespace with the "abi" namespace alias. libstdc++-v3/ChangeLog: * include/std/stacktrace: Do not include . (__cxa_demangle): Declare. --- libstdc++-v3/include/std/stacktrace | 8 +++- 1 f

[committed] libstdc++: Do not use #include inside push visibility scope [PR99871]

Tested powerpc64le-linux, pushed to trunk. -- >8 -- libstdc++-v3/ChangeLog: PR libstdc++/99871 * include/bits/specfun.h: Use visibility attribute on namespace, instead of pragma push/pop. * libsupc++/compare: Likewise. * libsupc++/exception: Likewise.

Re: [PATCH] libstdc++: Update documentation about copyright and GPL notices in tests

I've pushed this to trunk now. On Thu, 28 Apr 2022 at 18:02, Jonathan Wakely wrote: > > On Thu, 28 Apr 2022 at 17:45, Koning, Paul via Libstdc++ > wrote: > > > > > > > > > On Apr 28, 2022, at 8:37 AM, Jonathan Wakely via Gcc-patches > > > wrote: > > > > > > I intend to commit this patch soon.

[PATCH, OpenMP] Implement uses_allocators clause for target regions

Hi Jakub, this patch implements the uses_allocators clause for OpenMP target regions. For user defined allocator handles, this allows target regions to assign memory space and traits to allocators, and automatically calls omp_init/destroy_allocator() in the beginning/end of the target region. Fo

[PATCH] OpenMP, libgomp: Handle unified shared memory in omp_target_is_accessible.

Hi, This is a follow up patch of the patch that adds the OpenMP runtime routine omp_target_is_accessible: https://gcc.gnu.org/pipermail/gcc-patches/2022-March/591601.html It considers now also unified shared memory (usm) that was submitted recently (but not yet approved/committed): https:

Re: [Patch] OpenMP, libgomp: Add new runtime routine omp_target_is_accessible.

Hi Jakub, Am 05.05.2022 um 11:33 schrieb Jakub Jelinek: On Mon, Mar 14, 2022 at 04:42:14PM +0100, Marcel Vollweiler wrote: --- a/libgomp/libgomp.map +++ b/libgomp/libgomp.map @@ -226,6 +226,11 @@ OMP_5.1 { omp_get_teams_thread_limit_; } OMP_5.0.2; +OMP_5.1.1 { + global: +omp_target

Re: [PATCH v2 2/2] [PR100106] Reject unaligned subregs when strict alignment is required

On May 5, 2022, Segher Boessenkool wrote: > On Thu, May 05, 2022 at 08:59:21AM +0100, Richard Sandiford wrote: >> Alexandre Oliva via Gcc-patches writes: >> I know this is the best being the enemy of the good, but given >> that we're at the start of stage 1, would it be feasible to try >> to ge

Re: [PATCH][GCC 13] Enable match.pd dumping with -fdump-tree-original

On Fri, Mar 25, 2022 at 4:08 PM Alex Coplan via Gcc-patches wrote: > > Hi, > > I noticed that, while the C/C++ frontends invoke the GENERIC match.pd > simplifications to do early folding, the debug output from > generic-match.cc does not appear in the -fdump-tree-original output, > even with -fdum

[PATCH 1/2] xtensa: Rename deprecated extv/extzv insn patterns to extvsi/extzvsi

These patterns were deprecated since GCC 4.8. gcc/ChangeLog: * config/xtensa/xtensa.md (extvsi, extvsi_internal, extzvsi, extzvsi_internal): Rename from extv, extv_internal, extzv and extzv_internal, respectively. --- gcc/config/xtensa/xtensa.md | 16 1

[PATCH 2/2] xtensa: Reflect the 32-bit Integer Divide Option

On Espressif's ESP8266 (based on Tensilica LX106, no hardware divider), this patch reduces the size of each: __moddi3() @ libgcc.a : 969 -> 301 (saves 668) __divmoddi4() : -> 426 (saves 685) __udivmoddi4(): 1043 -> 319 (saves 724) in bytes, respectively. gcc/ChangeLo

Re: [1/2] PR96463 - aarch64 specific changes

Prathamesh Kulkarni writes: > diff --git a/gcc/config/aarch64/aarch64-sve-builtins-base.cc > b/gcc/config/aarch64/aarch64-sve-builtins-base.cc > index c24c0548724..1ef4ea2087b 100644 > --- a/gcc/config/aarch64/aarch64-sve-builtins-base.cc > +++ b/gcc/config/aarch64/aarch64-sve-builtins-base.cc >

Re: [PATCH][GCC 13] Enable match.pd dumping with -fdump-tree-original

Ping. https://gcc.gnu.org/pipermail/gcc-patches/2022-March/592307.html On 25/03/2022 15:07, Alex Coplan via Gcc-patches wrote: > Hi, > > I noticed that, while the C/C++ frontends invoke the GENERIC match.pd > simplifications to do early folding, the debug output from > generic-match.cc does not

GCC 9.4.1 Status Report (2022-05-06)

Status == The GCC 9 branch is in regression and documentation fixing mode. After the release of GCC 12.1 it's time to retire this branch and do a last release from it - GCC 9.5. I will do a GCC 9.5 release candidate in two weeks from now, May 20th, following by the release a week after tha

Re: [PATCH] Reconstruct i386 testsuite with __builtin_cpu_supports

On Fri, May 6, 2022 at 11:00 AM Hongyu Wang wrote: > > > I don't think *_os_support calls should be removed. IIRC, > > __builtin_cpu_supports function checks if the feature is supported by > > CPU, whereas *_os_supports calls check via xgetbv if OS supports > > handling of new registers. > > avx_o

[wwwdocs] GCC 12: OpenACC

Hi! Right in time for the GCC 12.1 release -- yay \o/ -- I've pushed to wwwdocs commit c6a7f816f3531d5727674620d74818fe1d150467 "GCC 12: OpenACC", see attached. Online: . Grüße Thomas - Siemens Electronic Design Automation GmbH;

Re: [PATCH] Reconstruct i386 testsuite with __builtin_cpu_supports

> I don't think *_os_support calls should be removed. IIRC, > __builtin_cpu_supports function checks if the feature is supported by > CPU, whereas *_os_supports calls check via xgetbv if OS supports > handling of new registers. avx_os_support is like avx_os_support (void) { unsigned int eax, ed

Re: [PATCH] [i386]Add combine splitter to transform pxor/pcmpeqb/pmovmskb/cmp 0xffff to ptest.

On Fri, May 6, 2022 at 10:01 AM Haochen Jiang wrote: > > Hi all, > > This patch aims to add a combine splitter to transform > pxor/pcmpeqb/pmovmskb/cmp 0x to ptest. > > Regtested on x86_64-pc-linux-gnu. Ok for trunk? > > BRs, > Haochen > > gcc/ChangeLog: > > PR target/104371 >

Re: [PATCH] [i386]Add combine splitter to transform pxor/pcmpeqb/pmovmskb/cmp 0xffff to ptest.

> +(define_split > + [(set (reg:CCZ FLAGS_REG) > + (compare:CCZ (unspec:SI > + [(eq:VI1_AVX2 > + (match_operand:VI1_AVX2 0 "vector_operand") > + (match_operand:VI1_AVX2 1 "const0_operand"))] > + UNSPE

Re: [PATCH] Reconstruct i386 testsuite with __builtin_cpu_supports

On Fri, May 6, 2022 at 9:57 AM Haochen Jiang wrote: > > Hi all, > > There are some check files in i386 testsuite are written before the function > __builtin_cpu_supports is introduced. All of them are using > __get_cpuid_count. This patch aims to reconstruct the i386 testsuite with > __builtin_

Re: [PATCH 11/12] aarch64: Make bti pass generic so it can be used by the arm backend

Andrea Corallo via Gcc-patches writes: > Hi all, > > this patch splits and restructures the aarch64 bti pass code in order > to have it usable by the arm backend as well. These changes have no > functional impact. > > Best Regards > > Andrea > > gcc/Changelog > > * config.gcc (aarch64*-*-

[PATCH] [i386]Add combine splitter to transform pxor/pcmpeqb/pmovmskb/cmp 0xffff to ptest.

Hi all, This patch aims to add a combine splitter to transform pxor/pcmpeqb/pmovmskb/cmp 0x to ptest. Regtested on x86_64-pc-linux-gnu. Ok for trunk? BRs, Haochen gcc/ChangeLog: PR target/104371 * config/i386/sse.md: Add new define_mode_attr and define_split. gcc/testsuit

[PATCH] Reconstruct i386 testsuite with __builtin_cpu_supports

Hi all, There are some check files in i386 testsuite are written before the function __builtin_cpu_supports is introduced. All of them are using __get_cpuid_count. This patch aims to reconstruct the i386 testsuite with __builtin_cpu_supports so that we can have a much clearer code. Regtested o