public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "gprocida at google dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29464] abidw performance regression on vmlinux
Date: Thu, 08 Sep 2022 09:28:29 +0000	[thread overview]
Message-ID: <bug-29464-9487-HehbxJcGdC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29464-9487@http.sourceware.org/bugzilla/>

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

--- Comment #6 from gprocida at google dot com ---
It turns out that there is now a new infinite loop in the XML writer when
compiled with Clang. This is our old "friend" where containers have
inconsistent equality and hash functions.

In particular:

Commit 7ecef636 "Canonicalize DIEs w/o assuming ODR & handle typedefs
transparently" introduced new sets and a map in the XML writer to track
referencing, emission and type ids for "non canonicalized" types as a separate
category.

It added non_canonicalized_type_equal and non_canonicalized_type_hash function
objects. The former is a deep equality and the latter hashes the non-internal
name.

The net effect is that I see a typedef being repeatedly emitted in a tight
loop. It's recorded as emitted but not found when checked to see if it was
emitted.

The last time these issues occurred they were eventually resolved by using much
safer and more efficient bare pointers as the keys to the containers.

I don't understand why new sets and maps were added or why they need to have
bespoke equality and hash functions.

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

  parent reply	other threads:[~2022-09-08  9:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09 17:57 [Bug default/29464] New: " gprocida at google dot com
2022-08-10 15:05 ` [Bug default/29464] " gprocida at google dot com
2022-08-22  9:37 ` dodji at redhat dot com
2022-09-01  9:03 ` dodji at redhat dot com
2022-09-06 16:00 ` gprocida at google dot com
2022-09-06 16:10 ` gprocida at google dot com
2022-09-06 16:37 ` gprocida at google dot com
2022-09-08  9:28 ` gprocida at google dot com [this message]
2022-09-19 10:19 ` dodji at redhat 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-29464-9487-HehbxJcGdC@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libabigail@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).