public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "mhov at undo dot io" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/27979] New: Performance regression of ~10% in conditional breakpoint testcase Date: Mon, 14 Jun 2021 12:44:46 +0000 [thread overview] Message-ID: <bug-27979-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=27979 Bug ID: 27979 Summary: Performance regression of ~10% in conditional breakpoint testcase Product: gdb Version: 10.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: mhov at undo dot io Target Milestone: --- Created attachment 13491 --> https://sourceware.org/bugzilla/attachment.cgi?id=13491&action=edit reproducer program There seems to be a performance regression from 9.2 to 10.2 that is observable in the time to run the following command on the attached reproducer program. This has been used to benchmark the performance of conditional breakpoints. $ gcc --version gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0 $ gcc -g repro.c $ ./gdb --batch --ex "b foo if bar==0x7ffffff" --ex "run" --args ./a.out Also attached is a log from the libera.chat #gdb channel where this regression was discussed. As can be seen in the attached chat log, bisection by Simon suggests that this commit is to blame: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=1009d92fc621bc4d017029b90a5bfab16e17fde5 I'm not currently in a position to delve deeper into this, so I'm posting here in case anyone wants to pick it up. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-06-14 12:44 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-14 12:44 mhov at undo dot io [this message] 2021-06-14 12:45 ` [Bug gdb/27979] " mhov at undo dot io 2021-06-14 12:47 ` mhov at undo dot io 2021-06-14 12:58 ` simark at simark dot ca 2021-06-14 15:21 ` ssbssa at sourceware 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-27979-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).