public inbox for
 help / color / mirror / Atom feed
From: Ian Lance Taylor <>
Subject: Re: .eh_frame problem
Date: Thu, 04 Mar 1999 14:32:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

   From: "Mark E." <>
   Date: Thu, 4 Mar 1999 00:15:52 -0500

   Here's the code:
   #define md_maybe_text() \
    ((bfd_get_section_flags (stdoutput, now_seg) & 
   SEC_CODE) != 0)
   #define md_maybe_text() \
    (now_seg != data_section && now_seg != 

   It seems to me, to parallel the BFD_ASSEMBER 
   version, that the !BFD_ASSEMBER version should 
   be something like:
   #define md_maybe_text() (now_seg == 

That would not be parallel, since when using COFF or ELF it is
possible for a section other than text_section to contain code.  This
will happen if you compile with -ffunction-sections, for example.


  reply	other threads:[~1999-03-04 14:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-02 21:56 Mark E.
1999-03-03 16:53 ` Ian Lance Taylor
1999-03-03 21:00   ` Mark E.
1999-03-03 21:15   ` Mark E.
1999-03-04 14:32     ` Ian Lance Taylor [this message]
1999-03-03  7:17 Mark E.

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).