From: rth@cygnus.com (Richard Henderson)
To: bfd@cygnus.com
Subject: Re: Further 97r2 cygwin32 problems
Date: Mon, 20 Oct 1997 16:51:00 -0000 [thread overview]
Message-ID: <62gqdn$c8t$1@dot.cygnus.com> (raw)
In-Reply-To: <199710202144.RAA02007.cygnus.bfd@subrogation.cygnus.com>
In article <199710202144.RAA02007.cygnus.bfd@subrogation.cygnus.com>,
Ian Lance Taylor <ian@cygnus.com> wrote:
>Good catch. Since this data is presumably read only, it might be
>better to put it in .rdata, instead, as below.
The current state of .eh_frame is that is does contain -- at least
for elf shared libraries -- runtime relocations. I don't know for
sure if this affects dll's but it seems like it would.
r~
parent reply other threads:[~1997-10-20 16:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <199710202144.RAA02007.cygnus.bfd@subrogation.cygnus.com>]
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='62gqdn$c8t$1@dot.cygnus.com' \
--to=rth@cygnus.com \
--cc=bfd@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).