From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16651 invoked by alias); 25 Mar 2002 23:06:05 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 16644 invoked from network); 25 Mar 2002 23:06:02 -0000 Received: from unknown (HELO dberlin.org) (64.246.6.106) by sources.redhat.com with SMTP; 25 Mar 2002 23:06:02 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by dberlin.org (8.11.6/8.11.6) with ESMTP id g2PN61m06816; Mon, 25 Mar 2002 18:06:01 -0500 Date: Mon, 25 Mar 2002 15:06:00 -0000 From: Daniel Berlin To: jimb@redhat.com cc: gdb@sources.redhat.com Subject: Getting rid of the symbol_ranges and aliases stuff Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-03/txt/msg00232.txt.bz2 If I implement the LOC_COMPUTED and LOC_COMPUTED_ARG, does anyone object to me removing SYMBOL_RANGES and SYMBOL_ALIASES in the process? Reasons: 1. The only thing that generates this is redhat internal, and I don't think that gcc even has it enabled by default. 2. It wastes 8 bytes in every symbol (because it's implemented at the wrong level). 3. It's STABS specific. 4. It's subsumed by LOC_COMPUTED. 5. It's probably not been tested in a *long* time, since only redhat internal gcc can generate the info, and it's not done by default. This is the live range splitting extensions to stabs stuff. It works by having multiple symbols that are aliases to a given symbol at a given PC. In effect, it uses multiple symbols to simulate DWARF2 location lists. It could be reimplemented in terms of location functions, cleanly. But since nothing publicly available generates the info, I can't do that as part of a LOC_COMPUTED and LOC_COMPUTED_ARG implementation. Nor do I think I should be required to. --Dan