From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A3F943858C5E; Wed, 14 Jun 2023 17:24:38 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A3F943858C5E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1686763478; bh=hyY6v4RMkELA4RDp0kw0zFyP4pk742Ll+XA02T2WFe0=; h=From:To:Subject:Date:From; b=XReSAI7TyXHS85hPYaAYz0HJuWvtooX+4PaBBrVwWIRqlHa6Zj0FJMmTRr517ghXn bURVpSirAmN5VV74HD5Gz0aGrXqQFc/fxMjkmvSOOGiRa7lc4MV4pPglPq+zt6OKO/ nadxlFk5GIQl0yAxscuVFV6ALkwYUbU05YfcxLgI= From: "stammark at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110255] New: arm: MVE intrinsics C++ polymorphism with -flax-vector-conversions Date: Wed, 14 Jun 2023 17:24:38 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new 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: stammark at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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=3D110255 Bug ID: 110255 Summary: arm: MVE intrinsics C++ polymorphism with -flax-vector-conversions Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: stammark at gcc dot gnu.org Target Milestone: --- Hi all, See: https://godbolt.org/z/53ME1fGfM The compiler with the error is the one that is using -flax-vector-conversio= ns through the C++ frontend. Unsure if this is something to do with the C++ front-end or something in the target backend (and how the builtins are registered with the front-end). This seems to happen regardless of if the vaddq intrinsic has been "restructured" by Christophe's https://gcc.gnu.org/pipermail/gcc-patches/2023-April/615997.html (so going = back to older GCC12,13 still gives the error), but another intrinsic, like vbicq, doesn't give the error at all (although that has a different context of the `int` immediate having to be a compile-time constant). (clang handles all this fine FWIW) Has anyone seen this kind of thing before, have any ideas on workarounds, or have any insight on if this this invalid C++ to begin with?=