From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 5CB0C385700E; Fri,  3 Mar 2023 19:10:12 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5CB0C385700E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1677870612;
	bh=FH6NFvMDsy9GTojcj+Fqb0GXR7497Gi/L+rF2OFX1ug=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=H3dwuXk/en0LLwSYILRn3Hvl9l2oneHrK9jec/K2vSTnUb2a/4uAk2ccb/mqkewvB
	 mRvOSBZFQvkRNZDmlqacumMBtUDrm/bDgWBE7LJiTkUvjcHLeiblxWJ/yUVT+KAESV
	 8L+e5QVp34vS4fbZBvGn3jBgwvjANsZEp27bkvTw=
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/51534] Bad code gen for vcgtq_u32 NEON intrinsic
Date: Fri, 03 Mar 2023 19:10:10 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-51534-4-OHII04aTz4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-51534-4@http.gcc.gnu.org/bugzilla/>
References: <bug-51534-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D51534

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Alexandre Oliva <aoliva@gcc.gnu.org>:

https://gcc.gnu.org/g:cc9cc5a9a5fb0c16532a16b87fbd155037a7ed89

commit r13-6457-gcc9cc5a9a5fb0c16532a16b87fbd155037a7ed89
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Fri Mar 3 15:59:21 2023 -0300

    [PR51534] [arm] split out pr51534 test for softfp

    The test uses arm_hard_ok and arm_softfp_ok as if they were mutually
    exclusive, but they test whether the corresponding -mfloat-abi=3D flag
    is usable, not whether it is in effect, so it is possible for both to
    pass, and then the test comes out with incorrect expectations
    whichever the default float-abi is.

    Separate the test into hard and softfp variants, and extend the softfp
    variant to accept both ARM and Thumb opcodes; it unwarrantedly assumed
    the latter.


    for  gcc/testsuite/ChangeLog

            PR target/51534
            * gcc.target/arm/pr51534.c: Split softfp variant into...
            * gcc.target/arm/pr51534s.c: ... this, and support ARM too.=