From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: from second.openwall.net (second.openwall.net [193.110.157.125]) by inbox.vuxu.org (Postfix) with SMTP id 2B373259DA for ; Thu, 9 May 2024 13:11:36 +0200 (CEST) Received: (qmail 24018 invoked by uid 550); 9 May 2024 11:11:31 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 22197 invoked from network); 9 May 2024 11:04:46 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715252677; x=1715857477; darn=lists.openwall.com; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=nG2RbwkjBGBPZMtyfbj7Yb6EfjFtN6fcVJHJFOGRlOs=; b=HfGFc7EHO44JMt6jaEFjwTk79GyyQFjzI9KyQ+zitKMhFnwgFNIDE5Zez/7wE7uNAT jpqhHdNhFOvW97SA/82xenrnSH9W0kELlVXDF0fIAsMvOK5iRhFmG2qVjLW2QhJtpE63 8K5JHNWZ3Lx19lKYCU67Q3RtwaWA6Cabm7ZE9TBPG7YVzG2dmqoQJN391ZqzwZkICUx+ HHVCyU87cB+IjlwrmHQ6Ki31m+6RTnTwxTV1WEs/a2dnWlveiju6If6rREJukFwgbO/J j1+MnXUiqQckLwvf23RoQfYTm6Yc2KtAb2Xd61a8J5CGZYEp8Iutlwwv3QWO8CzUB3an ja5Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715252677; x=1715857477; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=nG2RbwkjBGBPZMtyfbj7Yb6EfjFtN6fcVJHJFOGRlOs=; b=k7h0fofkq9+6EiooXlBoYNF+2ZDcW3Gl24Ci+7qP+mgWP+Nz4PbG7lS70EiONoollf DRl/39C8gJyxHaEoY6ILgq66w68uAoB2vlfPOv+kQ82WdfSYnf0uhsbxKgcvIwdJKbPw K2ftgm/jI4vCsXfIxgXjXSJdsYQB/EhFvrrm/W6I3PCtX0vXS9qkz8pI6MAVLLX+NLRN i3mRHIyWlQut3ljmidGY+aV9lTkqtUq7tNsjhzG9z6fzG2YwDhhHFOgk2iFySagkUNvX eMMwHxQGNW+uZbxFnLeMyuZTdvSu0Qe6UJSyo2Flt41Br4qh97NNk+yWSRCKC3dwGKUb hwbA== X-Gm-Message-State: AOJu0YzxHh6Dp8dYB6hMuZbJ2diK8gFBye+zwPLadXmWAesYomC6wg6s f02zag4hiCl2mMrlBTC/YQgrZoKHjB3pTxjSB7KSiS7+oxcaJf8hIdn47o+YuVm4HCxe0O5rgll Si3kUh5+1+HaJc6hqhqdDz7lQ4Q0hf07j X-Google-Smtp-Source: AGHT+IFW11ztPf23iC2Kdca6/X4ewjq2SgmvWsk0gtjw1FaM+kcfWZ+h4cEU2/bLHPf9Lnq4NFdkWC1DeHo7fuioms8= X-Received: by 2002:a4a:51c1:0:b0:5aa:596c:52d0 with SMTP id 006d021491bc7-5b24d634bd8mr5381165eaf.6.1715252677332; Thu, 09 May 2024 04:04:37 -0700 (PDT) MIME-Version: 1.0 From: Maxim Blinov Date: Thu, 9 May 2024 12:04:28 +0100 Message-ID: To: musl@lists.openwall.com Content-Type: text/plain; charset="UTF-8" Subject: [musl] IFUNC support Hi all, I just wanted to clarify the current status on IFUNCs, specifically when generated by the compiler when using the `target_clones` c function attribute. Am I correct that this is not currently supported by musl? If so, would musl ever support this feature, or is it rejected as a matter of principle? And lastly, if it is possible, what would it take to support this feature? I googled around for some previous discussions on the subject and found https://www.openwall.com/lists/musl/2022/08/23/7, and also https://www.openwall.com/lists/musl/2014/11/11/2, which reports IFUNCs as "One feature musl intentionally does not yet support", but I suppose I wanted to ask again since this was from 2014 and perhaps something has changed since then. I originally stumbled on this issue by observing that the musl dynamic linker, for x86_64, currently errors out on IFUNC symbols with ``` unknown relocation 37 ``` And on RISC-V it throws up with ``` unsupported relocation type 58 ``` which corresponds with the R_RISCV_IRELATIVE relocation. BR, Maxim