Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@cygnus.com>
To: fnf@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: Hopefully last one of these init_types() tweaks
Date: Sun, 09 Dec 2001 11:10:00 -0000	[thread overview]
Message-ID: <15379.47264.397391.436411@krustylu.cygnus.com> (raw)
In-Reply-To: <200112091815.fB9IF9e02565@fishpond.ninemoons.com>

Fred Fish writes:
 > Found one more case where init_types could simply be called with the
 > right flag bits rather than setting them after the fact.  I believe
 > this is the last one of these, except for one in java_lookup_class()
 > that is in code that is commented out and is broken code anyway.
 > 
 > -Fred


Yes, please commit it.

Thanks
Elena

 > 
 > 2001-12-09  Fred Fish  <fnf@redhat.com>
 > 
 > 	* mdebugread.c (cross_ref): Pass TYPE_FLAG_STUB to init_type()
 > 	rather than setting it after the type is created.
 > 
 > Index: mdebugread.c
 > ===================================================================
 > RCS file: /cvs/cvsfiles/devo/gdb/mdebugread.c,v
 > retrieving revision 2.88
 > diff -c -p -r2.88 mdebugread.c
 > *** mdebugread.c	2001/11/10 03:02:19	2.88
 > --- mdebugread.c	2001/12/08 21:20:59
 > *************** cross_ref (int fd, union aux_ext *ax, st
 > *** 4234,4241 ****
 >     if (rf == -1)
 >       {
 >         *pname = "<undefined>";
 > !       *tpp = init_type (type_code, 0, 0, (char *) NULL, current_objfile);
 > !       TYPE_FLAGS (*tpp) |= TYPE_FLAG_STUB;
 >         return result;
 >       }
 >   
 > --- 4234,4240 ----
 >     if (rf == -1)
 >       {
 >         *pname = "<undefined>";
 > !       *tpp = init_type (type_code, 0, TYPE_FLAG_STUB, (char *) NULL, current_objfile);
 >         return result;
 >       }
 >   


      reply	other threads:[~2001-12-09 19:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-09 10:21 Fred Fish
2001-12-09 11:10 ` Elena Zannoni [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=15379.47264.397391.436411@krustylu.cygnus.com \
    --to=ezannoni@cygnus.com \
    --cc=fnf@redhat.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