This is the mail archive of the gcc@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]
Other format: [Raw text]

Re: __attribute__((cleanup(function)) versus try/finally

On Wed, May 14, 2003 at 02:11:24PM -0700, Geoff Keating wrote:
> But that's the truly neat part of the plan, you don't need to make it
> robust.  All you need is to be able to look at RTL and determine
> whether the object-code reader will be successful in deducing the
> unwind information; if it would get it wrong, you just output explicit
> unwind information.

Oh, right.

You've got to maintain N+1 versions (rtl, plus N target assemblies)
of the same heuristics that (1) operate on different source languages
and (2) must be kept in exact sync lest we get incorrect results.

That sounds completely unmaintainable.

Lets just stick with dwarf2 unwind information, shall we?



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