public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/107727] New: error: multiversioning needs 'ifunc' which is not supported on this target (x86_64-w64-mingw32 target) Date: Wed, 16 Nov 2022 21:19:47 +0000 [thread overview] Message-ID: <bug-107727-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107727 Bug ID: 107727 Summary: error: multiversioning needs 'ifunc' which is not supported on this target (x86_64-w64-mingw32 target) Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: unlvsur at live dot com Target Milestone: --- #include<cstdio> [[__gnu__::__target__("avx2")]] inline void foo() { puts("avx2\n"); } [[__gnu__::__target__("default")]] inline void foo() { puts("default\n"); } int main() { foo(); } $ clang++ -o a a.cc --target=x86_64-windows-gnu -s -flto=thin -fuse-ld=lld $ wine a.exe avx2 $ x86_64-w64-mingw32-g++ -o a a.cc -s -flto a.cc: In function 'int main()': a.cc:10:13: error: multiversioning needs 'ifunc' which is not supported on this target 10 | inline void foo() | ^~~ a.cc:18:1: error: use of multiversioned function without a default 18 | } | ^
next reply other threads:[~2022-11-16 21:19 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-16 21:19 unlvsur at live dot com [this message] 2022-11-16 21:20 ` [Bug target/107727] " unlvsur at live dot com 2022-11-16 21:29 ` unlvsur at live dot com 2022-11-16 21:50 ` pinskia at gcc dot gnu.org 2022-11-16 21:50 ` [Bug middle-end/107727] " pinskia at gcc dot gnu.org 2022-11-16 21:51 ` pinskia 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-107727-4@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).