public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/27937] Performance regression of 8% due to assert in dwarf/read/attribute.h Date: Fri, 15 Apr 2022 13:58:04 +0000 [thread overview] Message-ID: <bug-27937-4717-6o5dEZ16RF@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27937-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27937 --- Comment #5 from Tom Tromey <tromey at sourceware dot org> --- A simple test like: /bin/time -f%e ~/gdb/install/bin/gdb -batch -nx -ex 'break internal_error' /tmp/gdb ... does not show any improvement with this assert commented out. So I wonder if it's still worthwhile. Commenting out all the asserts in attribute.h does increase that test's speed a little bit -- from ~2.06 to ~2.03 with a hot cache. https://github.com/tromey/gdb/commit/b3ed9b13eb970972b72842644a894d95b02b71b0 -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2022-04-15 13:58 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-01 8:30 [Bug symtab/27937] New: " vries at gcc dot gnu.org 2021-06-01 8:30 ` [Bug symtab/27937] " vries at gcc dot gnu.org 2021-06-01 15:26 ` ssbssa at sourceware dot org 2021-06-01 16:36 ` simark at simark dot ca 2021-06-01 21:12 ` tromey at sourceware dot org 2021-06-04 15:28 ` tromey at sourceware dot org 2022-04-15 13:31 ` tromey at sourceware dot org 2022-04-15 13:58 ` tromey at sourceware dot org [this message]
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-27937-4717-6o5dEZ16RF@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).