public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "i at maskray dot me" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/29584] New: gdb: support zstd compressed .gnu_debugdata Date: Mon, 19 Sep 2022 04:24:31 +0000 [thread overview] Message-ID: <bug-29584-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29584 Bug ID: 29584 Summary: gdb: support zstd compressed .gnu_debugdata Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: i at maskray dot me Target Milestone: --- .gnu_debugdata is compressed with xz, which is very slow to compress and decompress. zstd compressing with a large level (e.g. 18 used by Arch Linux packaging, 19 used by openSUSE packaging) can be slower than xz, but the output is much faster to decompress (e.g. time(xz -18) / time(zstd -18) > 5 for some workload). This depends on PR29563 . -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-09-19 4:24 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-19 4:24 i at maskray dot me [this message] 2022-09-19 4:24 ` [Bug gdb/29584] " i at maskray dot me 2022-09-27 2:54 ` i at maskray dot me 2023-02-16 2:55 ` i at maskray dot me 2023-02-16 6:15 ` tromey at sourceware dot org 2023-02-16 6:25 ` i at maskray dot me 2023-02-16 9:08 ` mark at klomp dot org 2023-02-16 17:42 ` i at maskray dot me 2023-02-16 21:46 ` tromey at sourceware dot org 2023-02-19 13:23 ` mark at klomp dot org 2023-02-19 19:24 ` i at maskray dot me 2024-03-15 9:16 ` sam at gentoo dot org
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=bug-29584-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).