This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Provide unwind info for x86, x86-64 (and s390{,x}) C++ thunks (PR target/43498)
- From: Jan Hubicka <hubicka at ucw dot cz>
- To: Jakub Jelinek <jakub at redhat dot com>, gcc-patches at gcc dot gnu dot org
- Date: Thu, 25 Mar 2010 01:28:33 +0100
- Subject: Re: [PATCH] Provide unwind info for x86, x86-64 (and s390{,x}) C++ thunks (PR target/43498)
- References: <20100324163540.GO2817@tyan-ft48-01.lab.bos.redhat.com>
> Hi!
>
> We don't emit unwind info on these targets for C++ thunks, while we do so e.g.
> for ppc/ppc64/ia64/sparc*.
> I've finally thought about just emitting .cfi_startproc/.cfi_endproc when
> -fdwarf2-cfi-asm, but as the thunks are emitted before .eh_frame with
> -fno-dwarf2-cfi-asm, it actually isn't any harder to handle it for both
> ways of emitting unwind info.
Note that original idea with defining unwinding in x86_64 ABI was that for
functions with no stack frame there should be no need for dwarf2 unwind info,
since the unwinders can easilly handle it themselves. This was meant primarily
to make unwinding through trampolines possible, but thunks falls into this category
too.
Honza