This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.

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

Re: c++/3099: cygwin: Many g++ EH failures

To: "Billinghurst, David (CRTS)" <David dot Billinghurst at riotinto dot com>, "'rth at gcc dot gnu dot org'" <rth at gcc dot gnu dot org>, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org
Subject: Re: c++/3099: cygwin: Many g++ EH failures
From: Richard Henderson <rth at redhat dot com>
Date: Wed, 13 Jun 2001 10:32:25 -0700
References: <8D00C32549556B4E977F81DBC24E985D1B1AA1@crtsmail1.technol_exch.corp.riotinto.org> <20010613112040.A7001@redhat.com>

On Wed, Jun 13, 2001 at 11:20:41AM -0400, Christopher Faylor wrote:
> If you can give me a clue about how to do this, I'll take a stab at it.

Hum.  That cygwin patch was pretty naive -- the startup process seems
to be more complicated than I estimated.  What needs to happen is 

  static struct object obj;
  __register_frame_info (__EH_FRAME_BEGIN__, &obj)

needs to get called before constructors run, and 

  __deregister_frame_info (__EH_FRAME_BEGIN__)

needs to get called after destructors run.  Like __CTOR_LIST__, 
__EH_FRAME_BEGIN__ is local to each dll or exe.


r~

References:
- RE: c++/3099: cygwin: Many g++ EH failures
  - From: Billinghurst, David (CRTS)
- Re: c++/3099: cygwin: Many g++ EH failures
  - From: Christopher Faylor

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