public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27979] Performance regression of ~10% in conditional breakpoint testcase
Date: Mon, 14 Jun 2021 12:58:34 +0000	[thread overview]
Message-ID: <bug-27979-4717-IfRd1u5Yc7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27979-4717@http.sourceware.org/bugzilla/>

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

Simon Marchi <simark at simark dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |simark at simark dot ca

--- Comment #2 from Simon Marchi <simark at simark dot ca> ---
Things to investigate:

 - We do a lot of work finding tailcalls even though no tailcalls are involved
the test case.  Is there a way we can do less work in this case?
 - On the fast path, while looking for tailcalls, a NO_ENTRY_VALUE_ERROR
exception is thrown.  It's probably not good to rely on exceptions being thrown
in the normal path of the program, maybe try to change that with functions
returning nullptr if they don't find anything.

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

  parent reply	other threads:[~2021-06-14 12:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-14 12:44 [Bug gdb/27979] New: " mhov at undo dot io
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 [this message]
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-IfRd1u5Yc7@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).