From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Type cleanups
Date: Sun, 12 May 2002 20:18:00 -0000 [thread overview]
Message-ID: <3CDF3081.1020900@cygnus.com> (raw)
In-Reply-To: <20020513003359.GA11672@nevyn.them.org>
> 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''.
Does this mean that ``struct type *'' is becoming opaque? Looking at
the next patch, no, sigh.
Andrew
> 2002-05-12 Daniel Jacobowitz <drow@mvista.com>
>
> * ax-gdb.c (gen_sign_extend, gen_fetch, gen_usual_unary)
> (gen_cast, gen_scale, gen_add, gen_sub, gen_binop, gen_deref)
> (gen_address_of, gen_struct_ref, gen_repeat): Use type
> access macros.
> * c-typeprint.c (cp_type_print_method_args): Likewise.
> (c_type_print_args): Likewise.
> * d10v-tdep.c (d10v_push_arguments): Likewise.
> (d10v_extract_return_value): Likewise.
> * expprint.c (print_subexp): Likewise.
> * gdbtypes.c (lookup_primitive_typename): Likewise.
> (lookup_template_type, add_mangled_type, print_arg_types): Likewise.
> * gdbtypes.h (TYPE_UNSIGNED, TYPE_NOSIGN, TYPE_STUB)
> (TYPE_TARGET_STUB, TYPE_STATIC, TYPE_CONST, TYPE_VOLATILE)
> (TYPE_PROTOTYPED, TYPE_INCOMPLETE, TYPE_CODE_SPACE, TYPE_VARARGS)
> (TYPE_VECTOR): Likewise.
> * hpread.c (hpread_read_struct_type)
> (fix_static_member_physnames, fixup_class_method_type)
> (hpread_type_lookup): Likewise.
> * mdebugread.c (parse_symbol, parse_type): Likewise.
> * p-lang.c (is_pascal_string_type): Likewise.
> * valops.c (hand_function_call): Likewise.
> * x86-64-tdep.c (classify_argument): Likewise.
>
> * hpread.c (hpread_read_function_type)
> (hpread_read_doc_function_type): Call replace_type.
> * dstread.c (create_new_type): Delete.
> (decode_dst_structure, process_dst_function): Call alloc_type.
> Use type access macros.
next prev parent reply other threads:[~2002-05-13 3:18 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 [this message]
2002-05-12 20:40 ` Daniel Jacobowitz
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=3CDF3081.1020900@cygnus.com \
--to=ac131313@cygnus.com \
--cc=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