public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "torbjorn.svensson at st dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tdep/29738] Arm M-profile dwarf2 unwinder performance suffers from exponential growth Date: Fri, 04 Nov 2022 15:27:38 +0000 [thread overview] Message-ID: <bug-29738-4717-rGJ3MMlrgG@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29738-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29738 Torbjörn SVENSSON <torbjorn.svensson at st dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |torbjorn.svensson at st dot com --- Comment #6 from Torbjörn SVENSSON <torbjorn.svensson at st dot com> --- I think this series addresses the issues raised here... https://sourceware.org/pipermail/gdb-patches/2022-November/193391.html @Tomas, can you take a look at them and see if it resolves the issues you've seen? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-11-04 15:27 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-31 18:18 [Bug tdep/29738] New: Arm v8 M-profile secure extension dwarf2 unwinder performance tomas.vanek at fbl dot cz 2022-11-02 8:16 ` [Bug tdep/29738] " luis.machado at arm dot com 2022-11-02 16:26 ` luis.machado at arm dot com 2022-11-03 8:20 ` luis.machado at arm dot com 2022-11-03 8:43 ` [Bug tdep/29738] Arm M-profile dwarf2 unwinder performance suffers from exponential grows tomas.vanek at fbl dot cz 2022-11-03 8:44 ` [Bug tdep/29738] Arm M-profile dwarf2 unwinder performance suffers from exponential growth tomas.vanek at fbl dot cz 2022-11-04 11:04 ` tomas.vanek at fbl dot cz 2022-11-04 15:27 ` torbjorn.svensson at st dot com [this message] 2023-02-02 3:43 ` brobecker at gnat dot com
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-29738-4717-rGJ3MMlrgG@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).