From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25963 invoked by alias); 13 Oct 2003 16:06:03 -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 25956 invoked from network); 13 Oct 2003 16:06:02 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 13 Oct 2003 16:06:02 -0000 Received: from drow by nevyn.them.org with local (Exim 4.24 #1 (Debian)) id 1A95Cr-0000Ii-FL for ; Mon, 13 Oct 2003 12:06:01 -0400 Date: Mon, 13 Oct 2003 16:06:00 -0000 From: Daniel Jacobowitz To: gdb-patches@gcc.gnu.org Subject: Re: [RFA] print function arguments for g95 Message-ID: <20031013160601.GA21537@nevyn.them.org> Mail-Followup-To: gdb-patches@gcc.gnu.org References: <20031013085319.GA865@twiddle.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031013085319.GA865@twiddle.net> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-10/txt/msg00426.txt.bz2 On Mon, Oct 13, 2003 at 01:53:19AM -0700, Richard Henderson wrote: > G95 properly represents function arguments as references. This > causes the current fortran support to hork. Fixed thus. Ok? Sure, thanks. > * f-typeprint.c (f_type_print_base): Handle TYPE_CODE_REF. > * f-valprint.c (f_val_print): Likewise. Tweak TYPE_CODE_PTR to > match c_val_print a bit closer. > > Index: f-typeprint.c > =================================================================== > RCS file: /cvs/src/src/gdb/f-typeprint.c,v > retrieving revision 1.11 > diff -u -p -r1.11 f-typeprint.c > --- f-typeprint.c 14 Sep 2003 16:32:12 -0000 1.11 > +++ f-typeprint.c 13 Oct 2003 08:48:03 -0000 > @@ -329,6 +329,11 @@ f_type_print_base (struct type *type, st > f_type_print_base (TYPE_TARGET_TYPE (type), stream, 0, level); > break; > > + case TYPE_CODE_REF: > + fprintf_filtered (stream, "REF TO -> ( "); > + f_type_print_base (TYPE_TARGET_TYPE (type), stream, 0, level); > + break; Does f_type_print_base take care of printing a closing paren or do you need one here? -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer