FAQ
PTAL

Now arm works a lot better, though still not 100%. Funny story: 5l
inserts calls to special routines called _div, _divu, _mod, and _modu to
implement the DIV and MOD pseudo-instructions. Those calls used to be
mentioned by the arm traceback routines, because the frame size was
slightly off during those calls. Now that the frame offset is recorded
correctly, that special case is gone from the traceback, so nothing was
holding up those routines to keep them in the binary, yet the linker was
still trying to use them. Now it knows to keep them from the start.


https://codereview.appspot.com/11085043/

--

---
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Search Discussions

  • Russ Cox at Jul 12, 2013 at 4:27 am
    PTAL

    arm is at 100% now. The final problem was the traceback didn't know to stop
    at runtime.mcall, which can be at the top of an m stack.

    --

    ---
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupgolang-dev @
categoriesgo
postedJul 12, '13 at 3:53a
activeJul 12, '13 at 4:27a
posts2
users1
websitegolang.org

1 user in discussion

Russ Cox: 2 posts

People

Translate

site design / logo © 2022 Grokbase