public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.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: Mon, 18 Mar 2024 08:47:26 +0000 [thread overview] Message-ID: <bug-114369-4-5IIw70VXHu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114369-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114369 --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- I'm inclined to close this as INVALID, but I'd accept working around the clang bug by, in system.h, guarded on __clang and powerpc, doing an #undef vec_step.
next prev parent reply other threads:[~2024-03-18 8:47 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-17 18:59 [Bug tree-optimization/114369] New: tree-vect-loop.cc uses vec_step which is also an altivec intrinsics pinskia at gcc dot gnu.org 2024-03-17 19:12 ` [Bug tree-optimization/114369] tree-vect-loop.cc uses vec_step which is also an altivec intrinsics breaks build when building with clang jakub at gcc dot gnu.org 2024-03-17 19:16 ` pinskia at gcc dot gnu.org 2024-03-17 19:53 ` gerald at pfeifer dot com 2024-03-18 8:47 ` rguenth at gcc dot gnu.org [this message] 2024-03-19 9:24 ` jakub at gcc dot gnu.org 2024-03-20 9:37 ` [Bug bootstrap/114369] " cvs-commit at gcc dot gnu.org 2024-03-30 3:54 ` cvs-commit at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-114369-4-5IIw70VXHu@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).