From: Heyi Guo <heyi.guo@linaro.org>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Zhu, Yonghong" <yonghong.zhu@intel.com>,
"Gao, Liming" <liming.gao@intel.com>
Subject: Why do we use -g option of gcc even for RELEASE build?
Date: Wed, 8 Nov 2017 10:25:14 +0800 [thread overview]
Message-ID: <145387dc-028f-c75f-6df3-cb0ead996eb8@linaro.org> (raw)
Hi folks,
From gcc manual, -g option seems to produce debugging information. In
tools_def.template, -g is included in GCC_ALL_CC_FLAGS, so it will also
be enabled for RELEASE build with gcc tool chain. Any special reason to
do that?
Thanks and regards,
Heyi
next reply other threads:[~2017-11-08 2:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 2:25 Heyi Guo [this message]
2017-11-08 14:53 ` Why do we use -g option of gcc even for RELEASE build? Laszlo Ersek
2017-11-08 15:32 ` Gao, Liming
2017-11-09 0:44 ` Heyi Guo
2017-11-08 15:49 ` Paolo Bonzini
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=145387dc-028f-c75f-6df3-cb0ead996eb8@linaro.org \
--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