public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/31237] [gdb, clang] FAIL: gdb.gdb/index-file.exp: gdb-index files are identical Date: Tue, 16 Jan 2024 10:55:08 +0000 [thread overview] Message-ID: <bug-31237-4717-VEAy69WL9Q@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31237-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31237 --- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> --- The cooked index consists of shards, and each shard has an address map, of type addrmap_mutable. The addr_mutable object supports overlapping insertion, but with insertion-order specific results. So, by changing the number of worker threads, we change the number of shards, and consequently the CUs indexed by each shard, and consequently the sequence of insertions into each per-shard address map. This is fine for the non-overlapping cases, we'd expect the same collection of <key,value> pairs, just distributed differently over the shards. But for the overlapping case, that doesn't work. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-16 10:55 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-12 8:13 [Bug gdb/31237] New: " vries at gcc dot gnu.org 2024-01-12 10:18 ` [Bug gdb/31237] " vries at gcc dot gnu.org 2024-01-12 10:19 ` vries at gcc dot gnu.org 2024-01-12 16:03 ` tromey at sourceware dot org 2024-01-13 1:56 ` tromey at sourceware dot org 2024-01-13 14:25 ` vries at gcc dot gnu.org 2024-01-13 14:54 ` vries at gcc dot gnu.org 2024-01-16 7:42 ` vries at gcc dot gnu.org 2024-01-16 10:55 ` vries at gcc dot gnu.org [this message] 2024-01-16 12:36 ` vries at gcc dot gnu.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-31237-4717-VEAy69WL9Q@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).