From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [RFC PATCH] meson.build: add -gsplit-dwarf to default cflags
Date: Mon, 3 Mar 2025 22:17:03 +0000 [thread overview]
Message-ID: <20250303221703.1291078-1-alex.bennee@linaro.org> (raw)
This option is supported by both gcc (since 4.7) and clang (since
7.0). Not only does this make the linkers job easier by reducing the
amount of ELF it needs to parse it also reduces the total build size
quite considerably. In my case a default build went from 5.8G to 3.9G.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
---
RFC:
- currently and RFC because it should also apply to test binaries
---
meson.build | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meson.build b/meson.build
index 4588bfd864..a936d1b422 100644
--- a/meson.build
+++ b/meson.build
@@ -363,7 +363,7 @@ endforeach
qemu_common_flags = [
'-D_GNU_SOURCE', '-D_FILE_OFFSET_BITS=64', '-D_LARGEFILE_SOURCE',
- '-fno-strict-aliasing', '-fno-common', '-fwrapv' ]
+ '-fno-strict-aliasing', '-fno-common', '-fwrapv', '-gsplit-dwarf' ]
qemu_cflags = []
qemu_ldflags = []
--
2.39.5
next reply other threads:[~2025-03-03 22:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 22:17 Alex Bennée [this message]
2025-03-04 10:19 ` [RFC PATCH] meson.build: add -gsplit-dwarf to default cflags Daniel P. Berrangé
2025-03-04 11:33 ` Alex Bennée
2025-03-04 11:38 ` Daniel P. Berrangé
2025-03-04 12:11 ` Daniel P. Berrangé
2025-03-04 13:20 ` Daniel P. Berrangé
2025-03-04 13:47 ` Alex Bennée
2025-03-04 13:40 ` Philippe Mathieu-Daudé
2025-03-04 13:43 ` Daniel P. Berrangé
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-all 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=20250303221703.1291078-1-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).