From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [RFC PATCH] meson.build: add -gsplit-dwarf to default cflags
Date: Tue, 4 Mar 2025 10:19:55 +0000 [thread overview]
Message-ID: <Z8bTy54Jgaddg6V3@redhat.com> (raw)
In-Reply-To: <20250303221703.1291078-1-alex.bennee@linaro.org>
On Mon, Mar 03, 2025 at 10:17:03PM +0000, Alex Bennée wrote:
> 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.
I've not come across this option before, but the docs say
‘-gsplit-dwarf’
If DWARF debugging information is enabled, separate as much
debugging information as possible into a separate output file with
the extension ‘.dwo’. This option allows the build system to avoid
linking files with debug information. To be useful, this option
requires a debugger capable of reading ‘.dwo’ files.
In Fedora and RHEL we build QEMU will full debug enabled, and then a feature
of the distro RPM build config will post-process all ELF files to extract
the debug info into files that we store under /usr/lib/debug. eg for
/usr/bin/qemu-system-x86_64, we get a separate
/usr/lib/debug/bin/qemu-system-x86_64-9.1.3-1.fc41.x86_64.debug, and
tools like GDB, etc know to look for these separate files.
When I test our RPM build process with this -gsplit-dwarf flag added,
we fail to find any debug symbols in the QEMU binaries and thus the
whole RPM package build aborts.
IOW, if we add this to QEMU, my best guess currently is that we're
going to have to revert it downstream.
>
> 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
>
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2025-03-04 10:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 22:17 [RFC PATCH] meson.build: add -gsplit-dwarf to default cflags Alex Bennée
2025-03-04 10:19 ` Daniel P. Berrangé [this message]
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=Z8bTy54Jgaddg6V3@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--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).