From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B9D6B3858D39; Sun, 17 Mar 2024 19:16:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B9D6B3858D39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1710702977; bh=fvFYIIkOPB5CcYZp6wqUi5WZxjcgoZcMCI6P1MMmBLU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=svGTAcdExhZZCyqG+s8tZ/KC7q0It+952BubU3O8UsntQTvXAqmt1OrImPaRauQFd SL/bU4L4YKLCZzPz0nzTEsHj8TmhabyOatNmCRMC1vWVa7mFvzb9rA+WegydVMSh7Q 8KxXYICs56dPm4rwtiA3U5OEek1sPLOOc+rAbkXY= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/114369] tree-vect-loop.cc uses vec_step which is also an altivec intrinsics breaks build when building with clang Date: Sun, 17 Mar 2024 19:16:17 +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: 14.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia 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: see_also 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=3D114369 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://github.com/llvm/llv | |m-project/issues/85579 --- Comment #2 from Andrew Pinski --- (In reply to Jakub Jelinek from comment #1) > The gcc altivec.h defines it as a function-like macro, so not a problem. > So perhaps a clang bug for not defining it as a function-like macro only? I filed it as https://github.com/llvm/llvm-project/issues/85579 also . Let's see what is mentioned htere.=