From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 64A03396DC29; Wed, 16 Nov 2022 21:50:10 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 64A03396DC29 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1668635410; bh=abB+qIOHYg3+MsH/jkYRlKJVT1FAZsCzzagaoIfGDmU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ASfG8pX6p/ICSvNO2Sj/2Sdc4BMWSm9T/U1AZNTtP+XSGrWYYRc0v5khe0inX4fTS OHg4rN1iUZGmpTQzTD2wB8pqH/iy3y6WTocVC8hN31IcVn2dduoOS0boP5jsNNrldR s5U0jPPyKSnkx4rH3ZugQ8wdXqasNkJKqKlrrYLU= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/107727] error: multiversioning needs 'ifunc' which is not supported on this target (x86_64-w64-mingw32 target) Date: Wed, 16 Nov 2022 21:50:10 +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: 13.0 X-Bugzilla-Keywords: 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: 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=3D107727 --- Comment #3 from Andrew Pinski --- What they do is basically have the resolver always called: callq __cpu_indicator_init movl __cpu_model+12(%rip), %eax andl $1024, %eax # imm =3D 0x400 cmpl $1024, %eax # imm =3D 0x400 sete %al andb $1, %al testb $1, %al jne .LBB1_1 jmp .LBB1_2 .LBB1_1: addq $40, %rsp jmp _Z3foov.avx2 # TAILCALL .LBB1_2: nop addq $40, %rsp jmp _Z3foov # TAILCALL Not the fastest way of implementing this either. A faster way to caching the result of the resolver. Anyways we currently don't support multiversioning for non-ifuncs supported targets. Someone will need to program up that support but it might be years unless you pay someone to do it.=