From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B7899388883F; Thu, 20 Jun 2024 06:45:27 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B7899388883F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1718865927; bh=xptiNR8qb+e7L+Kisp16iSNAX1HcorPNcK8SgzeSkTo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=KLxzcgadcNDaMrm0JyiLu7QY9YdCLVOK/WLGrqrU2tqDQGxV/yvP3Vs5xRt4p+szc p2CkdrHMy8vsy0Cc7HYyoA08TMcmTalo+46zhODwos/f31BMWsw2HubZ6mfEm20GLE DNWRzvsC+0HzMT5vvKRy8BwQDpaXYFzrOuZDkWRg= From: "rguenther at suse dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/115304] gcc.dg/vect/slp-gap-1.c FAILs Date: Thu, 20 Jun 2024 06:45:27 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 15.0 X-Bugzilla-Keywords: testsuite-fail X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenther at suse dot de X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 15.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D115304 --- Comment #13 from rguenther at suse dot de --- On Thu, 20 Jun 2024, pinskia at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D115304 >=20 > Andrew Pinski changed: >=20 > What |Removed |Added > -------------------------------------------------------------------------= --- > CC| |pinskia at gcc dot gnu.o= rg >=20 > --- Comment #12 from Andrew Pinski --- > Note when I am adding V4QI support to the aarch64 backend (emulating it v= ia > V8QI), I am getting a failure in slp-gap-1.c but it is different from the > others. >=20 > Without V4QI, the pattern matched `\{_\[0-9\]\+, 0` was able to match 6 t= imes. >=20 > we got in the IR: > ``` > unsigned int _50; > vector(2) unsigned int _49; > ... > _50 =3D MEM [(uint8_t *)vectp_pix1.5_58]; > _49 =3D {_50, 0}; > ``` >=20 >=20 > But afterwards we now get: > ``` > vector(4) unsigned char _50; > vector(8) unsigned char vect__34.9; > ... > _50 =3D MEM [(uint8_t *)vectp_pix1.5_58]; > vect__34.9_49 =3D {_50, { 0, 0, 0, 0 }}; > ``` >=20 > Which produces the exact same code. I am trying to figure out the best wa= y to > change the testcase pattern to make sure we don't match: > vect__37.23_6 =3D VEC_PERM_EXPR 8, 9, 10, 11 }>; >=20 > too. >=20 > `\{_\[0-9\]\+, { 0, 0` I think that will work but should I just do an > alternative for the scan-tree-dump-times or should I put it as a seperate= one > with some target selection here? Maybe match \{_\[0-9\]\+, (0\|{ 0(, 0)+ })? (with proper quoting)=