[git commit] libubacktrace: use -funwind-tables rather than -fexecptions

Mike Frysinger vapier at gentoo.org
Sat Dec 31 23:10:34 UTC 2011


On Thursday 22 December 2011 13:19:22 Carmelo AMOROSO wrote:
> On 22/12/2011 15.30, Carmelo Amoroso wrote:
> > commit:
> > http://git.uclibc.org/uClibc/commit/?id=8a8434b367e0b94b9fda72c99f1c6467
> > 37725403 branch:
> > http://git.uclibc.org/uClibc/commit/?id=refs/heads/master
> > 
> > For backtrace to work is enough to use -funwind-tables instead
> > of -fexceptions.
> > 
> > Signed-off-by: Carmelo Amoroso <carmelo.amoroso at st.com>
> 
> Indeed, I'm wondering if -fasynchrous-unwind-tables should be used
> rather then funwind-tables. On my arh SH4 the generated code is exactly
> the same. I'm not expert of DWARF, neither gcc documentation regarding
> the differences between -fexceptions, -funwind-tables or
> -fasynchronous-unwind-tables helped me so much.
> 
> someone else has clearer idea ?

for backtrace, we just want unwind-tables, so using that over -fexceptions is 
good (since we don't have to handle exceptions in this code).  as for the 
async vs non-async unwind-tables, i don't know the answer to that.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.busybox.net/pipermail/uclibc-cvs/attachments/20111231/d06e56e6/attachment.asc>


More information about the uClibc-cvs mailing list