From: "Marvin Häuser" <mhaeuser@posteo.de>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: devel@edk2.groups.io, Patrick Rudolph <patrick.rudolph@9elements.com>
Subject: Re: [edk2-devel] [PATCH 1/3] BaseTools/Conf/tools_def: Fix linking using CLANGDWARF_IA32_X64
Date: Wed, 15 Mar 2023 22:56:54 +0000 [thread overview]
Message-ID: <B6B28420-993D-456C-9FA6-A726C0828127@posteo.de> (raw)
In-Reply-To: <CAMj1kXECwHrEM_RQ3AbNbUnLU_fgNtFgd6EMzJ55OhM_Dn2Mdw@mail.gmail.com>
> On 15. Mar 2023, at 23:51, Ard Biesheuvel <ardb@kernel.org> wrote:
>
> On Wed, 15 Mar 2023 at 23:16, Marvin Häuser <mhaeuser@posteo.de> wrote:
>>
>> Hi,
>>
>> Why does the title mention X64? From what I can see, PIE is unaffected for X64 (and we really want it to be).
>>
>
> Why?
Why what? By “PIE is unaffected for X64” I meant by the patch (which only changes IA32 macros, no?). I can also see how the last part is a bit ambiguous, but I meant it literally - we really want X64 to be [unaffected] (which it is, by the patch, but the title implies otherwise, doesn’t it?).
Best regards,
Marvin
next prev parent reply other threads:[~2023-03-15 22:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 8:37 [PATCH 1/3] BaseTools/Conf/tools_def: Fix linking using CLANGDWARF_IA32_X64 Patrick Rudolph
2023-03-06 8:37 ` [PATCH 2/3] BaseTools/Conf/tools_def: Fix CLANGDWARF_IA32_X64 Patrick Rudolph
2023-03-06 8:39 ` Sean Rhodes
2023-03-15 16:52 ` [edk2-devel] " Sheng Lean Tan
2023-03-06 8:37 ` [PATCH 3/3] ShellPkg/TftpDynamicCommand.inf: Add missing DEPEX Patrick Rudolph
2023-03-06 8:39 ` Sean Rhodes
2023-03-15 16:54 ` [edk2-devel] " Sheng Lean Tan
2023-03-16 2:08 ` Gao, Zhichao
2023-03-15 16:45 ` [edk2-devel] [PATCH 1/3] BaseTools/Conf/tools_def: Fix linking using CLANGDWARF_IA32_X64 Sheng Lean Tan
[not found] ` <174CA58C1DBF1462.24874@groups.io>
2023-03-15 16:51 ` Sheng Lean Tan
2023-03-15 22:16 ` Marvin Häuser
2023-03-15 22:50 ` Ard Biesheuvel
2023-03-15 22:56 ` Marvin Häuser [this message]
2023-03-16 0:05 ` Ard Biesheuvel
2023-03-17 14:07 ` Patrick Rudolph
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=B6B28420-993D-456C-9FA6-A726C0828127@posteo.de \
--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