On Fri, Dec 9, 2016 at 9:26 AM, Mark Hatle <[email protected]> wrote: > On 12/9/16 12:48 AM, Khem Raj wrote: >> On Thu, Dec 8, 2016 at 11:03 AM, Mark Hatle <[email protected]> wrote: >>> +do_configure_append_arm () { >>> + echo "CFLAGS-abort.c = -funwind-tables" >> ${B}/configparms >>> + echo "CFLAGS-raise.c = -funwind-tables" >> ${B}/configparms >>> +} >> >> perhaps using -fasynchronous-unwind-tables is better. can you try that out ? >> > > This passed my internal test with the same results. > > So either one is fine with me. What is the difference between the options?
-fasynchronous-unwind-tables when used with -g emits the static data in dward2 into .debug_frame sections so your binaries dont bloat. funwind-tables is for generating static data that is needed for exception handing into .eh_frame. > > --Mark -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
