<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Feb 7, 2014, at 3:35 AM, Renato Golin <<a href="mailto:renato.golin@linaro.org">renato.golin@linaro.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 7 February 2014 09:35, Renato Golin <span dir="ltr"><<a href="mailto:renato.golin@linaro.org" target="_blank">renato.golin@linaro.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">Do we have such logic in Clang at the moment?<br>
</div></div></div></blockquote><div></div></div><br></div><div class="gmail_extra">Let me answer my own question. Right now, both -funwind-tables and -fno-unwind-tables only enable the -muniwind-tables for -cc1, and either lack or presence of that flag in -cc1 has the same behaviour on C++ code: they both generate .eh_frame sections.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">The only behaviour I found is that -munwind-tables will add uwtable to functions, which had no effect on x86_64. Is that because x86_64 mandates unwind tables?</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">If the semantics is that uwtable turns on tables on targets that don't require it (SjLj), but not that it turns off if missing on targets that mandate it, I can't use it to disable them on ARM. To be honest, recently, I'm not even sure I need, or want to disable. </div>
<div class="gmail_extra"><br></div><div class="gmail_extra">With Keith's patch to generate Dwarf unwind, the -arm-disable-ehabi flag could possibly be removed clean, and we can go directly to step 2.</div><div class="gmail_extra">
<br></div><div class="gmail_extra">Keith, Reid, are you happy with always generating unwind tables on ARM regardless?</div></div></blockquote><br></div><div>Just to double check, none of this will change the current behavior on Darwin, right?</div><div><br></div><div>-Jim</div><br></body></html>