From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A1A60385840E; Wed, 1 Nov 2023 01:23:15 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A1A60385840E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1698801795; bh=ZeY5suX3BFmpNHZ7nFBTIo34SHA5NIUyhZXmWNeFQiA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=SJUxJST8vb8MfTCKluQwNgvrq5xTDSeibQnr28EEVDa30s79PB/enyj3VbfuA3qvn 4B2sM0kkwywLWzB58YYYHwZ2ZvEXwFmjZaZxYhdiOQck9ZfC7KVNxkKV/L9gHj8JkG FsO1RPtkJQ9evobA9hXw7HpBTEneOv/wvJWNeXng= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112323] aarch64: C-operator support with ARM SVE intrinsic type Date: Wed, 01 Nov 2023 01:23:15 +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: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WONTFIX 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: resolution bug_status 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=3D112323 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #1 from Andrew Pinski --- https://gcc.gnu.org/pipermail/gcc-patches/2019-November/533558.html So the answer is no as far as I can tell. In fact: (5) It makes it easier to ensure that (with default options) code is portable between compilers without the GNU vector extensions having to become an official part of the SVE intrinsics spec. Is one of the big reasons. Though (1) might be even better reason. It is a bit odd that clang decided to go and implement it but this was a conscious decision to reject it and gave reasons why.=