public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
* .eh_frame problem
@ 1999-03-02 21:56 Mark E.
  1999-03-03 16:53 ` Ian Lance Taylor
  0 siblings, 1 reply; 6+ messages in thread
From: Mark E. @ 1999-03-02 21:56 UTC (permalink / raw)
  To: gas2

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?

Mark

--- 
Mark Elbrecht
snowball3@usa.net http://members.xoom.com/snowball3/

^ permalink raw reply	[flat|nested] 6+ messages in thread
* Re: .eh_frame problem
@ 1999-03-03  7:17 Mark E.
  0 siblings, 0 replies; 6+ messages in thread
From: Mark E. @ 1999-03-03  7:17 UTC (permalink / raw)
  To: gas2

> 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/

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~1999-03-04 14:32 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-03-02 21:56 .eh_frame problem 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
1999-03-03  7:17 Mark E.

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