qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [RFC PATCH] meson.build: add -gsplit-dwarf to default cflags
Date: Tue, 4 Mar 2025 14:40:31 +0100	[thread overview]
Message-ID: <902997f5-a2c8-4585-a834-5cde5aee98a1@linaro.org> (raw)
In-Reply-To: <Z8bt7ajRVwdabG7p@redhat.com>

On 4/3/25 13:11, Daniel P. Berrangé wrote:
> On Tue, Mar 04, 2025 at 11:33:44AM +0000, Alex Bennée wrote:
>> Daniel P. Berrangé <berrange@redhat.com> writes:
>>
>>> 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.
>>
>> A modern gdb can certainly handle fetching the debug out of the .dwo
>> files when debugging.
> 
> See this response from one of the upstream GCC maintainers pretty much
> recommending against (on by default) use of -gsplit-dwarf:
> 
>    https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/RXA55BTO62NWWHCTUFYGEVHJKZPL5EKE/

Jakub said:

  "it can be useful for fast modify/rebuild/test cycles during
   development, but is something that is really undesirable for
   the distro builds."

Do distro use --enable-debug by default? Otherwise it might be
useful to add it for developers.



  parent reply	other threads:[~2025-03-04 13:41 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é
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é [this message]
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=902997f5-a2c8-4585-a834-5cde5aee98a1@linaro.org \
    --to=philmd@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --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).