Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Use TYPE_TAG_NAME everywhere
Date: Sun, 03 Feb 2002 15:18:00 -0000	[thread overview]
Message-ID: <20020203181853.A28319@nevyn.them.org> (raw)
In-Reply-To: <20020203181542.A27182@nevyn.them.org>

On Sun, Feb 03, 2002 at 06:15:42PM -0500, Daniel Jacobowitz wrote:
> One file accessed the tag_name member directly.  Just for consistency, I
> fixed it to use the macro.  Committed as obvious.

Of course I missed one.  Fixed so.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer

Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.2122
diff -u -p -r1.2122 ChangeLog
--- ChangeLog	2002/02/03 23:11:33	1.2122
+++ ChangeLog	2002/02/03 23:17:49
@@ -1,5 +1,10 @@
 2002-02-03  Daniel Jacobowitz  <drow@mvista.com>
 
+	* gdbtypes.c (init_simd_type): Use TYPE_TAG_NAME instead of
+	accessing tag_name directly.
+
+2002-02-03  Daniel Jacobowitz  <drow@mvista.com>
+
 	* ax-gdb.c (find_field): Use TYPE_TAG_NAME instead
 	of accessing tag_name directly.
 
Index: gdbtypes.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbtypes.c,v
retrieving revision 1.39
diff -u -p -r1.39 gdbtypes.c
--- gdbtypes.c	2002/02/03 22:57:56	1.39
+++ gdbtypes.c	2002/02/03 23:17:49
@@ -809,7 +809,7 @@ init_simd_type (char *name,
   t = init_type (TYPE_CODE_STRUCT, n * TYPE_LENGTH (elt_type), 0, 0, 0);
   t->nfields = 1;
   t->fields = f;
-  t->tag_name = name;
+  TYPE_TAG_NAME (t) = name;
 
   return t;
 }


  reply	other threads:[~2002-02-03 23:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-03 15:15 Daniel Jacobowitz
2002-02-03 15:18 ` Daniel Jacobowitz [this message]
2002-02-03 16:27 ` Andrew Cagney

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=20020203181853.A28319@nevyn.them.org \
    --to=drow@mvista.com \
    --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