From: "Ard Biesheuvel" <ardb@kernel.org>
To: "Marvin Häuser" <mhaeuser@posteo.de>
Cc: "Shi, Steven" <steven.shi@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Yang, JiyangX" <jiyangx.yang@intel.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Sami Mujawar <sami.mujawar@arm.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
Supreeth Venkatesh <supreeth.venkatesh@arm.com>,
Vitaly Cheptsov <vit9696@protonmail.com>
Subject: Re: [edk2-devel] [PATCH v1 1/1] StandaloneMmPkg: To support CLANGPDB build
Date: Thu, 14 Oct 2021 11:09:53 +0200 [thread overview]
Message-ID: <CAMj1kXHkMy_OX-ZC45WpOB3aoegTryT2H+0rwyw1cXnfrOZ8Lw@mail.gmail.com> (raw)
In-Reply-To: <62e21365-66cf-353e-b139-cb8c64aa4fd7@posteo.de>
On Thu, 14 Oct 2021 at 11:08, Marvin Häuser <mhaeuser@posteo.de> wrote:
>
> Hey Steven,
>
> As I said, I prefer my patch, but this would work too of course.
> I talked about the PIE stuff with Ard before, so maybe he has an opinion
> on this? :)
>
> (Small correction for my last e-mail, of course we are not *guaranteed*
> there are *no* relocations in .text, but they'd all point to GOT (or
> whatever else the target uses for PIE), and references will probably be
> relative; for ARM architectures I remember Ard talking about specific
> kinds of relocations being avoided entirely).
>
Hello all,
As I understand it, we are talking about a native PE/COFF toolchain
here that does not rely on GenFw for ELF to PE/COFF conversion, right?
If so, there is no way the self-relocation is going to work anyway, so
whether we pass -fpie or not for AArch64 is immaterial here.
next prev parent reply other threads:[~2021-10-14 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 3:12 [PATCH v1 0/1] StandaloneMmPkg: To support CLANGPDB build jiyangx.yang
2021-10-14 3:12 ` [PATCH v1 1/1] " Jiyang Yang
2021-10-14 8:05 ` Marvin Häuser
2021-10-14 9:02 ` [edk2-devel] " Steven Shi
2021-10-14 9:08 ` Marvin Häuser
2021-10-14 9:09 ` Ard Biesheuvel [this message]
2021-10-14 9:13 ` Marvin Häuser
2021-10-14 13:14 ` Steven Shi
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=CAMj1kXHkMy_OX-ZC45WpOB3aoegTryT2H+0rwyw1cXnfrOZ8Lw@mail.gmail.com \
--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