public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "gaoliming" <gaoliming@byosoft.com.cn>
To: "'JoeX Lu'" <pen-chunx.lu@intel.com>, <devel@edk2.groups.io>
Subject: 回复: [edk2-devel] 回复: [edk2-devel] [PATCH] Support GLOBAL_REMOVE_IF_UNREFERENCED in GCC5/11
Date: Fri, 5 May 2023 11:15:00 +0800	[thread overview]
Message-ID: <004a01d97eff$c6df3f20$549dbd60$@byosoft.com.cn> (raw)
In-Reply-To: <6468.1683245062489518402@groups.io>

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

Joe:

 Such warning message in RELEASE build is expected. I suggest to disable them by compiler option.  If so, we don’t need to modify source code. 

 

Thanks

Liming

发件人: JoeX Lu <pen-chunx.lu@intel.com> 
发送时间: 2023年5月5日 8:04
收件人: gaoliming <gaoliming@byosoft.com.cn>; devel@edk2.groups.io
主题: Re: [edk2-devel] 回复: [edk2-devel] [PATCH] Support GLOBAL_REMOVE_IF_UNREFERENCED in GCC5/11

 

Hi Liming,
  For question1: We might declaim some variables/functions only used in DEBUG mode and those are necessary variables/functions for debugging but will trigger warning message in RELEASE build.

  For question2: Yes


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

  reply	other threads:[~2023-05-05  3:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28  2:46 [PATCH] Support GLOBAL_REMOVE_IF_UNREFERENCED in GCC5/11 JoeX Lu
2023-04-28  4:46 ` [edk2-devel] " Pedro Falcato
2023-04-28  5:53   ` JoeX Lu
2023-05-04  6:58     ` 回复: " gaoliming
2023-05-05  0:04       ` [edk2-devel] " JoeX Lu
2023-05-05  3:15         ` gaoliming [this message]
2023-05-05  4:47           ` [edk2-devel] 回复: " JoeX Lu

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='004a01d97eff$c6df3f20$549dbd60$@byosoft.com.cn' \
    --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