From: "Mark E." <snowball3@usa.net>
To: gas2@cygnus.com
Subject: Re: .eh_frame problem
Date: Wed, 03 Mar 1999 07:17:00 -0000 [thread overview]
Message-ID: <199903031517.PAA28568@out2.ibm.net> (raw)
> Could somebody from binutils read the thread archived at
> http://egcs.cygnus.com/ml/egcs-patches/1999-02/msg00547.html . It's
> a thread about a padding problem with .eh_frame and at least DJGPP.
> According to the egcs folks, this problem needs to be solved in gas. Are
> they right?
I forgot to mention DJGPP (i[34567]-pc-msdosdjgpp) uses COFF.
I wonder if .eh_frame should be given flagged like a data section (like
.edata and others are) in sec_to_stype_flags and in
style_to_sec_flags. Then wouldn't .eh_frame be padded with 0x0
instead of 0x90 (NOP) as it currently is?
Mark
---
Mark Elbrecht
snowball3@usa.net http://members.xoom.com/snowball3/
next reply other threads:[~1999-03-03 7:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-03 7:17 Mark E. [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=199903031517.PAA28568@out2.ibm.net \
--to=snowball3@usa.net \
--cc=gas2@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).