From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21062 invoked by alias); 17 Dec 2009 16:53:32 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 21052 invoked by uid 22791); 17 Dec 2009 16:53:30 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Date: Thu, 17 Dec 2009 16:53:00 -0000 From: Daniel Jacobowitz To: Paul Pluzhnikov Cc: Tom Tromey , archer@sourceware.org Subject: Re: Initial psymtab replacement results Message-ID: <20091217165321.GA28783@caradoc.them.org> References: <20091211235901.GA16889@caradoc.them.org> <20091214230947.GA31362@caradoc.them.org> <8ac60eac0912170838r39c6916cte5a54a458a859010@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <8ac60eac0912170838r39c6916cte5a54a458a859010@mail.gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-SW-Source: 2009-q4/txt/msg00119.txt.bz2 On Thu, Dec 17, 2009 at 08:38:52AM -0800, Paul Pluzhnikov wrote: > On Mon, Dec 14, 2009 at 3:09 PM, Daniel Jacobowitz wrote: > > > Mappable data structures are > > tricky; one thing I'd definitely insist on is host neutrality.  IMO > > that is not optional. > > I am sorry for being slow, but I thought about it for a while and I > still can't come up with a realistic scenario where the host > non-neutrality of the cache matters. > > Are you worried about hosts A and B (with different architecture) both > NFS-mounting server:/usr/lib/debug ? That already wouldn't work, > since e.g. libc-X.Y.Z.so.debug is not host-neutral. You obviously use a lot of native toolchains :-) In GDB terms, libc-X.Y.Z.so is host neutral. It's not target neutral. The terms shift if you're talking about building glibc; build/host aren't a great match for this scenario. If I'm going to ship pre-cached ARM Linux files, I need them to work on x86-linux and x86-mingw32 at a minimum. Sometimes I need them to work on sparc-solaris2.10 or powerpc-linux or arm-linux. That's where I was coming from. If we can limit it to endianness, and maybe pointer size, then we can put that in the cache key as Frank suggested. Then this goes away, or at least doesn't bother me so much. -- Daniel Jacobowitz CodeSourcery