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: generating functions and eh region


On Fri, 3 Apr 2009, Ian Lance Taylor wrote:
> gcc's -fasynchronous-unwind-tables option is
> intended to support unwinding the stack at any precise instruction
> boundary, which might be adequate for this purpose if the OS can handle
> the adjustment from an exception in the middle of an instruction to an
> exception after the previous instruction is complete.  Unfortunately,
> -fasynchronous-unwind-tables doesn't work; unwinding the stack during a
> function epilogue is not handled correctly.

FWIW, that's what I've once thought, but different GCC people
have different opinions on the extent of exceptions that
-fasynchronous-unwind-tables can and should enable.  For example
some Richards exclude prologue and epilogue and/or stack-slot
accesses.

Just pointing out that there's no consensus on what's a bug and
what's a reasonable limitation of -fasynchronous-unwind-tables.
I'm not sure there is consensus among the GNAT people either.

brgds, H-P


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