From: "Ard Biesheuvel" <ardb@kernel.org>
To: devel@edk2.groups.io, mhaeuser@posteo.de,
Liming Gao <gaoliming@byosoft.com.cn>, Ray Ni <ray.ni@intel.com>
Cc: Rebecca Cran <rebecca@bsdio.com>, Bob Feng <bob.c.feng@intel.com>,
"Chen, Christine" <yuwei.chen@intel.com>,
"Rudolph, Patrick" <patrick.rudolph@9elements.com>,
Lean Sheng Tan <sheng.tan@9elements.com>,
Pedro Falcato <pedro.falcato@gmail.com>,
Vitaly Cheptsov <vit9696@protonmail.com>,
Leif Lindholm <quic_llindhol@quicinc.com>,
Steven Shi <steven.shi@intel.com>
Subject: Re: [edk2-devel] Role of DLINK2_FLAGS and link-time option consistency
Date: Fri, 7 Apr 2023 14:00:22 +0200 [thread overview]
Message-ID: <CAMj1kXFg1gmDRT8Nub_zmc+yJHDVCAQ+fs3c3X5iZ+Da6JV1mA@mail.gmail.com> (raw)
In-Reply-To: <846CCDAB-F758-4767-8588-17D65529415F@posteo.de>
(cc Ray)
On Fri, 7 Apr 2023 at 13:05, Marvin Häuser <mhaeuser@posteo.de> wrote:
>
>
> On 7. Apr 2023, at 13:02, Ard Biesheuvel <ardb@kernel.org> wrote:
>
> IIRC DLINK2_FLAGS is mainly being used (in the GCC case) for passing
> options that need to come after previous occurrences of the same
> option with a different value, in order for the DLINK2 one to take
> precedence.
>
>
> Thanks for the quick response! By that rationale, it should probably apply to the 16-bit ASM linker step as well and the rest can remain as-is (modulo that weird CLANGDWARF optimization situation)?
>
That build rule seems like dead code to me: we don't have any such
files in the repo, and no references to the .com output files that it
produces, afaict
(The last uses were removed in 1a48fda5315433661c2f3039a30aea5916c22267)
Maybe Ray can comment?
next prev parent reply other threads:[~2023-04-07 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 10:13 Role of DLINK2_FLAGS and link-time option consistency Marvin Häuser
2023-04-07 11:02 ` [edk2-devel] " Ard Biesheuvel
2023-04-07 11:05 ` Marvin Häuser
2023-04-07 12:00 ` Ard Biesheuvel [this message]
2023-04-15 19:33 ` Marvin Häuser
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=CAMj1kXFg1gmDRT8Nub_zmc+yJHDVCAQ+fs3c3X5iZ+Da6JV1mA@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