Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pierre Muller <muller@ics.u-strasbg.fr>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Add support for TYPE_CODE_FLAGS in fortran_val_print.
Date: Mon, 19 Aug 2002 06:16:00 -0000	[thread overview]
Message-ID: <4.2.0.58.20020819150949.02026288@ics.u-strasbg.fr> (raw)
In-Reply-To: <4.2.0.58.20020819140438.00ab64d0@ics.u-strasbg.fr>

As stated by Daniel Jacobowitz <drow@false.org>
the patch to use TYPE_CODE_FLAGS was never approved. 
This makes of course this RFA completely useless for now...

At 14:14 19/08/2002 , Pierre Muller a écrit:


>As already said in the previous mail, fortran language support
>is currently borken for i386 flags printing.
>
>Writing this mail, I noticed that I didn't mention the addition of the "c-nag.h" 
>include in my previous patch, is the following ChangeLog entry better?
>The ada source wil probably not suffer from the same problem
>as the default case is to call the c_val_print function.
>
>ChangeLog entry
>
>2002-08-19  Pierre Muller  <muller@ics.u-strasbg.fr>
>
>           * f-valprint.c: Add "c-lang.h" dependency needed for TYPE_CODE_FLAGS support.
>         (fortran_val_print): Add support for TYPE_CODE_FLAGS.
>          
>
>$ cvs diff -u -p f-valprint.c
>Index: f-valprint.c
>===================================================================
>RCS file: /cvs/src/src/gdb/f-valprint.c,v
>retrieving revision 1.6
>diff -u -p -r1.6 f-valprint.c
>--- f-valprint.c        7 Mar 2001 02:57:08 -0000       1.6
>+++ f-valprint.c        19 Aug 2002 12:12:24 -0000
>@@ -30,6 +30,7 @@
>   #include "valprint.h"
>   #include "language.h"
>   #include "f-lang.h"
>+#include "c-lang.h"
>   #include "frame.h"
>   #include "gdbcore.h"
>   #include "command.h"
>@@ -364,6 +365,11 @@ f_val_print (struct type *type, char *va
>     CHECK_TYPEDEF (type);
>     switch (TYPE_CODE (type))
>       {
>+
>+    case TYPE_CODE_FLAGS:
>+      return c_val_print (type, valaddr, embedded_offset, address, stream,
>+                         format, deref_ref, recurse, pretty);
>+
>       case TYPE_CODE_STRING:
>         f77_get_dynamic_length_of_aggregate (type);
>         LA_PRINT_STRING (stream, valaddr, TYPE_LENGTH (type), 1, 0);
>
>
>
>Pierre Muller
>Institut Charles Sadron
>6,rue Boussingault
>F 67083 STRASBOURG CEDEX (France)
>mailto:muller@ics.u-strasbg.fr
>Phone : (33)-3-88-41-40-07  Fax : (33)-3-88-41-40-99



Pierre Muller
Institut Charles Sadron
6,rue Boussingault
F 67083 STRASBOURG CEDEX (France)
mailto:muller@ics.u-strasbg.fr
Phone : (33)-3-88-41-40-07  Fax : (33)-3-88-41-40-99


      reply	other threads:[~2002-08-19 13:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-19  5:19 Pierre Muller
2002-08-19  6:16 ` Pierre Muller [this message]

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=4.2.0.58.20020819150949.02026288@ics.u-strasbg.fr \
    --to=muller@ics.u-strasbg.fr \
    --cc=gdb-patches@sources.redhat.com \
    /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