Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: gdb-patches@sources.redhat.com
Subject: [patch] ``struct value'' cleanups
Date: Sat, 16 Mar 2002 17:04:00 -0000	[thread overview]
Message-ID: <3C93EB92.2030003@cygnus.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 217 bytes --]

Hello,

The attatched are some simple cleanups for ``struct value''.  Committed.

Andrew

PS: As far as I can tell, the unused bit of code was added '94 and from 
day one it included the comment ``when is this used'.

[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 1201 bytes --]

2002-03-16  Andrew Cagney  <ac131313@redhat.com>

	* value.h (struct value): Delete field ``substring_addr''.  Change
	aligner fields to force_doublest_align, force_longest_align,
	force_core_addr_align and force_pointer_align.

Index: value.h
===================================================================
RCS file: /cvs/src/src/gdb/value.h,v
retrieving revision 1.27
diff -u -r1.27 value.h
--- value.h	2002/03/16 02:57:42	1.27
+++ value.h	2002/03/17 00:52:51
@@ -125,14 +125,6 @@
        list.  */
     struct value *next;
 
-    /* ??? When is this used?  */
-    union
-      {
-	CORE_ADDR memaddr;
-	char *myaddr;
-      }
-    substring_addr;
-
     /* Register number if the value is from a register.  Is not kept
        if you take a field of a structure that is stored in a
        register.  Shouldn't it be?  */
@@ -166,9 +158,10 @@
     union
       {
 	long contents[1];
-	double force_double_align;
-	LONGEST force_longlong_align;
-	char *literal_data;
+	DOUBLEST force_doublest_align;
+	LONGEST force_longest_align;
+	CORE_ADDR force_core_addr_align;
+	void *force_pointer_aligh;
       }
     aligner;
     /* Do not add any new members here -- contents above will trash them */

             reply	other threads:[~2002-03-17  1:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-16 17:04 Andrew Cagney [this message]
2002-03-16 17:17 ` Daniel Jacobowitz
2002-03-16 17:28   ` 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=3C93EB92.2030003@cygnus.com \
    --to=ac131313@cygnus.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