This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: unwind info for .init/.fini sections

From: Ulrich Drepper <drepper at redhat dot com>
To: libc-hacker at sources dot redhat dot com
Cc: David Mosberger-Tang <davidm at hpl dot hp dot com>
Date: 25 Feb 2002 21:00:41 -0800
Subject: Re: unwind info for .init/.fini sections
References: <m3r8nevyqb.fsf@myware.mynet>
Reply-to: drepper at redhat dot com (Ulrich Drepper)

David Mosberger <davidm@hpl.hp.com>
>  (1) Change the linker so it updates the unwind info once the final
>      .init/.fini section has been created.  This shouldn't be all
>      that hard: it requires updating the unwind table entry and
>      adjusting the unwind descriptors so that the final body region
>      is long enough to cover the entire section.
> 
>  (2) Require that each code fragment that goes into the .init/.fini
>      section is wrapped like this:
> 
> 		.proc whatever
> 		.prologue
> 		.vframe r32
> 		.save rp, r33
> 		.save ar.pfs, r34
> 		.body
> 		  :
> 		ACTUAL INIT CODE
> 		  :
> 		.endp

I definitely prefer (1).  Putting this kind of strange requirements on
the code is definitely causing problems.  Let things be automated as
much as possible.

-- 
---------------.                          ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Red Hat          `--' drepper at redhat.com   `------------------------

References:
- unwind info for .init/.fini sections
  - From: Ulrich Drepper

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]