<div dir="ltr"><div>Hi Renato,<br><br>Although replacing ARM-specific directives in favor of CFI directives is a desirable movement, I think the compatibility should be considered carefully before we stop to emit the ARM-specific directives.<br>
<br>Maybe a reasonable criteria is that there are at least two major releases of GNU binutils assembler which can emit EHABI tables by reading CFI directives?<br><br>Sincerely,<br></div><div>Logan<br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Sun, Mar 16, 2014 at 2:47 AM, 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 class="">On 15 March 2014 17:06, Logan Chien <<a href="mailto:tzuhsiang.chien@gmail.com">tzuhsiang.chien@gmail.com</a>> wrote:<br>
> I would like to know what do you mean by "commoning them up"?<br>
<br>
</div>Hi Logan,<br>
<br>
That'd be reducing ARM directives in favour of CFI, but as I said (and<br>
you too), GNU compatibility will probably be an issue for a very long<br>
time.<br>
<div class=""><br>
<br>
> For the space issue, I personally don't think this is a big issue. For the<br>
> code without exception handling, only stack informations will be encoded.<br>
> Besides, the encoding format is very compact. In the common cases, the code<br>
> without exception handling needs only 8-12 bytes per function. If this is<br>
> still an issue, then -fno-unwind-table might be a solution (i.e. at llvm<br>
> assembly level, the function should be marked with nounwind and without<br>
> uwtable.)<br>
<br>
</div>Yes, and that's what my merge request implements:<br>
<br>
<a href="http://llvm-reviews.chandlerc.com/D3079" target="_blank">http://llvm-reviews.chandlerc.com/D3079</a><br>
<br>
As soon as that's in, I believe EHABI is finally in good shape to be<br>
called Beta.<br>
<br>
Since the 3.4 release I'm trying to get the EHABI and IAS support in<br>
good shape (removing the final restraints, testing a lot), for them to<br>
be enabled by default in 3.5, and I think we got it, thanks to you,<br>
Anton, Saleem and many others.<br>
<br>
cheers,<br>
--renato<br>
</blockquote></div><br></div>