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.133.124]) by mx.groups.io with SMTP id smtpd.web10.67129.1680519854904167764 for ; Mon, 03 Apr 2023 04:04:15 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=L2M+wuMD; spf=pass (domain: redhat.com, ip: 170.10.133.124, mailfrom: kraxel@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1680519854; 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: in-reply-to:in-reply-to:references:references; bh=sAxYdPwQmY6qjt1qcXjJPeKGUALD+YWn+JnpUmxxw/M=; b=L2M+wuMDYHaVrBr54iWNRlSlkuv2BrCpUliexv/y5xztzHL0IQ3v9Zf+AZFpYpEY2IJqhx FzyASJ26ukVJFsuhJa8i+XcjJvpr3iryRdQRcWj/rY+5vmfWyiK1kuJOXhgGmMeYa0KKbL XYUkeZD/9PPQlvc7y68Zrficf+RIm6A= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-626-20Wsy4FKOjW20LGAI7IkAg-1; Mon, 03 Apr 2023 07:04:08 -0400 X-MC-Unique: 20Wsy4FKOjW20LGAI7IkAg-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 5114C3C18340; Mon, 3 Apr 2023 11:04:08 +0000 (UTC) Received: from sirius.home.kraxel.org (unknown [10.39.193.241]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 04D302166B26; Mon, 3 Apr 2023 11:04:08 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id A445C1800393; Mon, 3 Apr 2023 13:04:06 +0200 (CEST) Date: Mon, 3 Apr 2023 13:04:06 +0200 From: "Gerd Hoffmann" To: devel@edk2.groups.io, mcb30@ipxe.org Cc: lichao@loongson.cn, maobibo@loongson.cn, WANG Xuerui , qemu-devel , Song Gao , =?utf-8?B?5p2o5bCP5aif?= Subject: Re: [edk2-devel] On integrating LoongArch EDK2 firmware into QEMU build process Message-ID: References: <1f1d3d9f-c3df-4f29-df66-886410994cc3@xen0n.name> <67517424-0f32-09f8-6446-53f71ebd59b5@loongson.cn> <317e3008-e2bd-8af6-2cf5-dad49d98cb8d@loongson.cn> <0102018746aa8382-eabf5475-59a6-4741-a8b1-ca3d5b49da92-000000@eu-west-1.amazonses.com> MIME-Version: 1.0 In-Reply-To: <0102018746aa8382-eabf5475-59a6-4741-a8b1-ca3d5b49da92-000000@eu-west-1.amazonses.com> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Apr 03, 2023 at 10:29:52AM +0000, Michael Brown wrote: > On 03/04/2023 11:13, Chao Li wrote: > > This problem is because the gcc-12 does not yet to support the option > > 'mno-explicit-reloc', this option is used to open the new reloaction > > type for LoongArch, this new feature is very important for LoongArch, > > because it can reduce the binary size and improve code execution > > efficiency, so we turn it on when submitting the code to the EDK2 repo. > > Is it possible to produce a _functional_ LoongArch64 EDK2 binary without > this option, even if the resulting binary is less efficient? MdePkg/Include/IndustryStandard/PeImage.h lists a single loongarch relocation type only, which I expect being the new type. So I suspect the answer is "no" because the edk2 pe loader isn't able to handle the old relocation type(s). take care, Gerd