From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mx.groups.io with SMTP id smtpd.web10.5159.1643363512475338248 for ; Fri, 28 Jan 2022 01:51:52 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=NDpyd1YW; spf=pass (domain: redhat.com, ip: 170.10.129.124, mailfrom: kraxel@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1643363511; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=eNzhaNpYaCUn2IKEn7jH3a+rYNt6U5dbhPQulepOvZg=; b=NDpyd1YWVehwwxc9ZIzzqHkHBVMry9+R7aZD5K5PMT75i3m44NZ5QYN/ENsXo/9yEImv1+ j7nRH+Xtrf4R5LmllWr+hamuvmmmDO4HJ+2txeV5I+dQXQJbigOmryTPRcw15urAmLh0sG xSN0/B7CeyVdO9PW4B5DaOc7vw7khLg= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-395-X671T4-3PKyUSzCwZghf0w-1; Fri, 28 Jan 2022 04:51:46 -0500 X-MC-Unique: X671T4-3PKyUSzCwZghf0w-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id AFB298519E0; Fri, 28 Jan 2022 09:51:44 +0000 (UTC) Received: from sirius.home.kraxel.org (unknown [10.39.193.47]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 44C6F66E00; Fri, 28 Jan 2022 09:51:43 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id 864E51800608; Fri, 28 Jan 2022 10:51:41 +0100 (CET) Date: Fri, 28 Jan 2022 10:51:41 +0100 From: "Gerd Hoffmann" To: devel@edk2.groups.io, afish@apple.com Cc: "KILIAN_KEGEL@outlook.com" , Mike Kinney , "Yao, Jiewen" , Sean Brogan , Bret Barkelew , "Wang, Jian J" , "Jiang, Guomin" , Pawel Polawski , "Lu, XiaoyuX" , Pedro Falcato Subject: Re: [edk2-devel] [PATCH 00/24] CryptoPkg/openssl: update openssl submodule to v3.0 Message-ID: <20220128095141.igvraq64j7e5obv6@sirius.home.kraxel.org> References: <20220117114627.ji5cyqxkca6bmiaf@sirius.home.kraxel.org> <20220121083035.dsqzu3akshonliza@sirius.home.kraxel.org> <20220126110244.klk24znojvdtirzw@sirius.home.kraxel.org> <71737233-2840-42CE-A65E-1895E936B4CB@apple.com> MIME-Version: 1.0 In-Reply-To: <71737233-2840-42CE-A65E-1895E936B4CB@apple.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=kraxel@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit On Thu, Jan 27, 2022 at 04:55:37PM -0800, Andrew Fish via groups.io wrote: > Very cool idea but ….. > > 1) We don’t always use the systems native compiler and sometimes we use a cross compiler so making assumptions about system libs is not always valid. The intrinsics ship with the cross compiler, so that shouldn't be much of a problem. I have a bunch of them here: kraxel@sirius ~# locate libgcc.a /usr/lib/gcc/aarch64-linux-gnu/11/libgcc.a /usr/lib/gcc/arm-linux-gnueabi/11/libgcc.a /usr/lib/gcc/i686-w64-mingw32/11.2.1/libgcc.a /usr/lib/gcc/riscv64-linux-gnu/11/libgcc.a /usr/lib/gcc/riscv64-linux-gnu/11/lib32/ilp32/libgcc.a /usr/lib/gcc/riscv64-linux-gnu/11/lib32/ilp32d/libgcc.a /usr/lib/gcc/riscv64-linux-gnu/11/lib64/lp64/libgcc.a /usr/lib/gcc/riscv64-linux-gnu/11/lib64/lp64d/libgcc.a /usr/lib/gcc/x86_64-linux-gnu/11/libgcc.a /usr/lib/gcc/x86_64-linux-gnu/11/32/libgcc.a /usr/lib/gcc/x86_64-redhat-linux/11/libgcc.a /usr/lib/gcc/x86_64-redhat-linux/11/32/libgcc.a /usr/lib/gcc/x86_64-w64-mingw32/11.2.1/libgcc.a > On a Mac with Xcode clang I’ve got full SysV ABI libs (not supper helpful for EFI), but not EFI/MSFT x86_64 ABI. I don't think the system libs matter at all for uefi builds as they are free-standing. > 2) Are these system libs architecturally defined to be free standing? That seems to be more of a problem, libgcc has calls into libc ... take care, Gerd