From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13384 invoked by alias); 9 Jul 2002 22:10:00 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 13370 invoked from network); 9 Jul 2002 22:09:59 -0000 Received: from unknown (HELO zwingli.cygnus.com) (208.245.165.35) by sources.redhat.com with SMTP; 9 Jul 2002 22:09:59 -0000 Received: by zwingli.cygnus.com (Postfix, from userid 442) id B559E5EA11; Tue, 9 Jul 2002 17:09:58 -0500 (EST) To: Andrew Cagney Cc: Daniel Berlin , gdb-patches@sources.redhat.com Subject: Re: [RFA]: dwarf2expr.[ch] References: <3D2A5D2C.5040506@ges.redhat.com> From: Jim Blandy Date: Tue, 09 Jul 2002 15:21:00 -0000 In-Reply-To: <3D2A5D2C.5040506@ges.redhat.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-07/txt/msg00168.txt.bz2 Andrew Cagney writes: > Is there also a way of implementing these objects such that they > check, at compile time, a match between initialized members and those > that require assignment? Perhaphs a memset(0) will be easiest. What do you mean by "these objects"? Actually, that reminds me --- the function new_dwarf_expr_context is supposed to initialize all the function pointer entries to things that give an error message --- so that if the caller doesn't provide something, but the expression requires it, you get an error. > I suspect, for instance, you'll need to add a thread_local_storgage() > method pretty soon :-) Yeah, struct dwarf_expr_context will need a method for DW_OP_GNU_push_tls_address to fall back on.