public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "julien.torres at synopsys dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/24889] From gdb 8.1, major performance issue with all the commands involving a symbol lookup on class members of SystemC types
Date: Wed, 03 Mar 2021 13:54:39 +0000	[thread overview]
Message-ID: <bug-24889-4717-w5hTK3xeRO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24889-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=24889

--- Comment #3 from Julien <julien.torres at synopsys dot com> ---
Hi Simon,

I have made some benchmarks on the attached example with various gdb versions.

gdb version   Time in seconds
gdb 8.0.1        2.3
gdb 8.1         10.0
gdb 8.3         10.1
gdb 9.1          5.8
gdb 9.2          6.0
gdb 10.1         4.9

As you can see, things have been significantly improved in 9.1 and 10.1, but it
is still significantly slower than with 8.0.1.

I have found the issue with some programs using SystemC. But this probably
affects other programs which use lots of complex template classes and types (as
SystemC does).

So it would be be great if someone could have a look at the issue.

Thanks.

Julien

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-03-03 13:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-24889-4717@http.sourceware.org/bugzilla/>
2021-03-02 14:53 ` julien.torres at synopsys dot com
2021-03-02 16:04 ` simark at simark dot ca
2021-03-03 13:54 ` julien.torres at synopsys dot com [this message]
2021-03-03 14:09 ` cbiesinger at google dot com
2021-03-03 14:14 ` julien.torres at synopsys 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-24889-4717-w5hTK3xeRO@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: 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 read-only IMAP folder(s) and NNTP newsgroup(s).