From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8207 invoked by alias); 26 Jun 2007 23:08:09 -0000 Received: (qmail 8197 invoked by uid 22791); 26 Jun 2007 23:08:08 -0000 X-Spam-Check-By: sourceware.org Received: from shell4.bayarea.net (HELO shell4.bayarea.net) (209.128.82.1) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 26 Jun 2007 23:08:06 +0000 Received: (qmail 16746 invoked from network); 26 Jun 2007 16:08:04 -0700 Received: from 209-128-106-254.bayarea.net (HELO ?192.168.20.7?) (209.128.106.254) by shell4.bayarea.net with SMTP; 26 Jun 2007 16:08:04 -0700 Message-ID: <46819C43.7040506@eagercon.com> Date: Tue, 26 Jun 2007 23:08:00 -0000 From: Michael Eager User-Agent: Thunderbird 1.5.0.9 (X11/20070102) MIME-Version: 1.0 To: Jim Blandy CC: gdb@sources.redhat.com Subject: Re: Non-uniform address spaces References: <467D4AE3.7020505@eagercon.com> <20070623212557.GB3448@caradoc.them.org> <467D9503.9060804@eagercon.com> <46800482.4020700@eagercon.com> <46801FDD.4020408@eagercon.com> <468047F0.7060207@eagercon.com> <46814B4C.7080302@eagercon.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-06/txt/msg00321.txt.bz2 Jim Blandy wrote: > Michael Eager writes: >> Perhaps. I'll look at that. How does this work for TLS now? > > You probably want to start at dwarf2expr.c, and look at our > implementation of DW_OP_GNU_push_tls_address. That's invoking a > callback of which dwarf2loc.c:dwarf_expr_tls_address is a reasonable > representative. You can follow forward from there. I'll take a look. > Backing up a bit, I should ask: is contributing this work to the > public sources one of your goals? If it's not, I'm happy to answer > questions as best I can, but I shouldn't spend too much time on it. > If it is, then we (meaning the GDB developers, including you) need to > go at this in detail, starting with the meaning of the source > language, its ABI, its representation in the debugging info, the > facilities of the machine it's running on, and how the language > achieves its semantics on that machine. This is not going to go well > if there's just a big patch at the end. :) Yes, contributing to public sources is a goal. There are always factors which complicate this. - Working in different versions of GDB, with the need to port modifications from one version to another. There have been many changes in GDB which make code non-portable between different versions. - An interest in making minimal changes to solve a problem rather than engage in a major redesign effort. I'm helping the folks who are developing the UPC support for GDB. The sources are available on-line. I understand that they have an interest in submitting patches to support UPC when the code is a bit more stable. There's support in DWARF for UPC features, but the UPC language extensions have not yet been incorporated into the current version of GCC. -- Michael Eager eager@eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077