public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tracy Kuhrt <Tracy.Kuhrt@microchip.com>
To: binutils@sourceware.cygnus.com
Subject: COFF .endef Handling of def_symbol_in_progress
Date: Thu, 06 Sep 2001 09:45:00 -0000	[thread overview]
Message-ID: <3B97A82C.4B617E22@microchip.com> (raw)

In the obj_coff_endef function, the following exists:

static void
obj_coff_endef (ignore)
     int ignore ATTRIBUTE_UNUSED;
{
...
 /* Set the section number according to storage class.  */
  switch (S_GET_STORAGE_CLASS (def_symbol_in_progress))
    {
...
    case C_FCN:
      {
        CONST char *name;
        S_SET_SEGMENT (def_symbol_in_progress, text_section);

Why is the def_symbol_in_progress' section set to the text_section
versus now_seg?  If the compiler/user defines a section that is located
in the code section and is requesting debug information the .bf and .ef
symbols for a function in that section appear in the text section versus
the user-defined section.  Is this the correct behavior?

Tracy



             reply	other threads:[~2001-09-06  9:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-06  9:45 Tracy Kuhrt [this message]
2001-09-07  1:39 ` Nick Clifton

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=3B97A82C.4B617E22@microchip.com \
    --to=tracy.kuhrt@microchip.com \
    --cc=binutils@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).