public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Marvin Häuser" <mhaeuser@posteo.de>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
	Rebecca Cran <rebecca@bsdio.com>,
	Liming Gao <gaoliming@byosoft.com.cn>,
	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 11:05:04 +0000	[thread overview]
Message-ID: <846CCDAB-F758-4767-8588-17D65529415F@posteo.de> (raw)
In-Reply-To: <CAMj1kXGvPJmZp5Xm_XsXpkatFnDMmHmVcvmXjU3_2vCOEEre+g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 503 bytes --]


> 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)?


[-- Attachment #2: Type: text/html, Size: 3270 bytes --]

  reply	other threads:[~2023-04-07 11:05 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 [this message]
2023-04-07 12:00     ` Ard Biesheuvel
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=846CCDAB-F758-4767-8588-17D65529415F@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