From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 680463858C53; Tue, 3 Jan 2023 09:57:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 680463858C53 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1672739839; bh=BsQr+vRzX7GX+XB12s8V3sBap6RZqgmZtZt3PysSENo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=B8j4CxIczjazpM6rSWYhw+PHi1VQj6cZzdytsgjJL//KqEhlnZTVWmtnKjldz9kCa 0g8tji0FKCVa4gTVcwa2jah8UxFkUhHDWzzgXOSNXZP1L+L9jwCQ+uEG1igDMK0pM5 8mSFbOWA8bfjlR7efLvk3xCjksyygKa9WSwH9cX4= From: "mark at klomp dot org" To: gdb-prs@sourceware.org Subject: [Bug remote/28489] Allow caching of remote objfiles Date: Tue, 03 Jan 2023 09:57:18 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mark at klomp dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D28489 Mark Wielaard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mark at klomp dot org --- Comment #3 from Mark Wielaard --- (In reply to Simon Marchi from comment #2) > (In reply to Tom Tromey from comment #1) > > One possible issue here is that the cache might have to be > > per-remote, to deal with the situation where there is > > a cross-architecture build-id clash. Perhaps just encoding > > the arch into the cache file name is enough, though. >=20 > Isn't the concept of build-id that we can assume they are always unique, = for > all practical intents? I don't understand what situation you imagine whe= re > there would be a clash. yes, the idea is that build-ids are globally unique identifiers. But there = is no mechanism to enforce that. It just relies on the producer/linker to crea= te a large enough hash. --=20 You are receiving this mail because: You are on the CC list for the bug.=