From: "Gerd Hoffmann" <kraxel@redhat.com>
To: devel@edk2.groups.io, mcb30@ipxe.org
Cc: lichao@loongson.cn, maobibo@loongson.cn,
"WANG Xuerui" <i.qemu@xen0n.name>,
qemu-devel <qemu-devel@nongnu.org>,
"Song Gao" <gaosong@loongson.cn>, 杨小娟 <yangxiaojuan@loongson.cn>
Subject: Re: [edk2-devel] On integrating LoongArch EDK2 firmware into QEMU build process
Date: Mon, 3 Apr 2023 13:04:06 +0200 [thread overview]
Message-ID: <wkju3vayu3e2wtqmxakigrliv7ifj4ecd7ympkgwlacf7h4ckx@jnkqqqujdycf> (raw)
In-Reply-To: <0102018746aa8382-eabf5475-59a6-4741-a8b1-ca3d5b49da92-000000@eu-west-1.amazonses.com>
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
next prev parent reply other threads:[~2023-04-03 11:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1f1d3d9f-c3df-4f29-df66-886410994cc3@xen0n.name>
[not found] ` <67517424-0f32-09f8-6446-53f71ebd59b5@loongson.cn>
[not found] ` <x5vbhjcyc3jl5u3qdjg2dq2znwhdq7ordmbjm6s2hftwyusqp2@r6smasorrjor>
[not found] ` <317e3008-e2bd-8af6-2cf5-dad49d98cb8d@loongson.cn>
2023-04-03 8:51 ` On integrating LoongArch EDK2 firmware into QEMU build process maobibo
2023-04-03 10:13 ` [edk2-devel] " Chao Li
2023-04-03 10:29 ` Michael Brown
2023-04-03 11:04 ` Gerd Hoffmann [this message]
2023-04-04 2:24 ` Chao Li
2023-04-03 10:58 ` Gerd Hoffmann
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-list 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=wkju3vayu3e2wtqmxakigrliv7ifj4ecd7ympkgwlacf7h4ckx@jnkqqqujdycf \
--to=devel@edk2.groups.io \
/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: link
Be 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