From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@gcc.gnu.org
Subject: Re: [RFA] print function arguments for g95
Date: Mon, 13 Oct 2003 16:06:00 -0000 [thread overview]
Message-ID: <20031013160601.GA21537@nevyn.them.org> (raw)
In-Reply-To: <20031013085319.GA865@twiddle.net>
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
next prev parent reply other threads:[~2003-10-13 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 8:55 Richard Henderson
2003-10-13 16:06 ` Daniel Jacobowitz [this message]
2003-10-14 6:53 ` Richard Henderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031013160601.GA21537@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox