Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Type cleanups
Date: Sun, 12 May 2002 20:40:00 -0000	[thread overview]
Message-ID: <20020513034024.GA27096@nevyn.them.org> (raw)
In-Reply-To: <3CDF3081.1020900@cygnus.com>

On Sun, May 12, 2002 at 11:18:25PM -0400, Andrew Cagney wrote:
> >In order to fix gdb/277, I needed to move a lot of members of 'struct 
> >type'. This patch flushes out all (that I could find) direct accesses of 
> >these
> >members instead of through the proper macros.  It's possible that I missed
> >some; if so, the next patch will cause whichever files I missed to stop
> >compiling.  I'm pretty sure I got them all, though.  I also clean up the
> >only remaining references to 'sizeof (struct type)': dstread.c had a clone
> >of alloc_type, and hpread.c needed to call replace_type like the other
> >readers.
> >
> >This patch should have no effect.  On i386-linux, I get byte-for-byte
> >identical GDB binaries (all 5591185 bytes of it, debugging information
> >and all; no -g3 here).
> >
> >OK to commit?
> 
> Did you check all the cross targets build per MAINTAINERS?  From memory 
> sh-hms[bfd] and avr[need to look] don't build at present (well as of 
> ~2002-05-12-gmt).
> 
> If that has been checked, then yes ``obviously''.

I'll do that.  Sigh, takes forever... least there are scripts for it.

BTW, the fragment of awk in MAINTAINERS only works with GNU awk.

> Does this mean that ``struct type *'' is becoming opaque?  Looking at 
> the next patch, no, sigh.

No.  It's accessed so frequently that switching from macros to accessor
functions would be a ridiculous performance hit, I think.

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


  reply	other threads:[~2002-05-13  3:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-12 17:34 Daniel Jacobowitz
2002-05-12 20:18 ` Andrew Cagney
2002-05-12 20:40   ` Daniel Jacobowitz [this message]
2002-05-12 21:31     ` Andrew Cagney
2002-05-13 11:46       ` Daniel Jacobowitz
2002-05-13 12:54         ` Daniel Berlin
2002-05-13 12:57           ` Daniel Jacobowitz
2002-05-13  6:59   ` Daniel Jacobowitz
2002-05-13  8:37     ` Andrew Cagney
2002-05-13  8:51       ` Elena Zannoni
2002-05-13  9:11         ` Andrew Cagney
2002-05-13  9:19           ` Elena Zannoni
2002-05-13 11:50       ` Daniel Jacobowitz
2002-05-13 11:59         ` Daniel Jacobowitz
2002-05-13 15:14           ` Andrew Cagney
2002-05-13 16:09             ` Daniel Jacobowitz
2002-05-13 18:37               ` Elena Zannoni
2002-05-14 17:09               ` Andrew Cagney
2002-05-17  1:11     ` Eli Zaretskii
2002-05-17  8:02       ` Daniel Jacobowitz
2002-05-17  9:14         ` Eli Zaretskii
2002-05-17 10:21           ` Daniel Jacobowitz
2002-05-17 10:34             ` Andrew Cagney
2002-05-18  0:15               ` Eli Zaretskii
2002-05-18  0:13             ` Eli Zaretskii

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=20020513034024.GA27096@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=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