Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [rfa] ENUM_BITFIELD, here it comes again
Date: Wed, 20 Aug 2003 07:52:00 -0000	[thread overview]
Message-ID: <vt2ptj0vkec.fsf@zenia.home> (raw)
In-Reply-To: <200308200249.h7K2ni62029448@duracef.shout.net>


Michael Elizabeth Chastain <mec@shout.net> writes:
> Here we go again ... a new version of my ENUM_BITFIELD patch.
> +/* Classification types for this symbol.  These should be taken as "advisory
> +   only", since if gdb can't easily figure out a classification it simply
> +   selects mst_unknown.  It may also have to guess when it can't figure out
> +   which is a better match between two types (mst_data versus mst_bss) for
> +   example.  Since the minimal symbol info is sometimes derived from the
> +   BFD library's view of a file, we need to live with what information bfd
> +   supplies. */

Some of this comment needs to stay in the struct, and some needs to
stick with the enum.


       reply	other threads:[~2003-08-20  7:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200308200249.h7K2ni62029448@duracef.shout.net>
2003-08-20  7:52 ` Jim Blandy [this message]
2003-08-21 19:49 [rfa] ENUM BITFIELD, " Michael Elizabeth Chastain
  -- strict thread matches above, loose matches on Subject: below --
2003-08-21 18:57 Michael Elizabeth Chastain
2003-08-21 19:19 ` Andrew Cagney
2003-08-21 17:42 Michael Elizabeth Chastain
2003-08-21 18:46 ` Andrew Cagney
2003-08-20 17:42 Michael Elizabeth Chastain
     [not found] <200308201639.h7KGd6BX008220@duracef.shout.net>
2003-08-20 17:36 ` [rfa] ENUM_BITFIELD, " Jim Blandy
2003-08-20 16:49 [rfa] ENUM BITFIELD, " Michael Elizabeth Chastain
2003-08-21 13:48 ` Andrew Cagney
2003-08-20  2:50 [rfa] ENUM_BITFIELD, " Michael Elizabeth Chastain

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=vt2ptj0vkec.fsf@zenia.home \
    --to=jimb@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