You're mistaken here. At call point, call through PLT looks normal. That's the whole point.
-
-
No extra code is generated for thr call itself, but some archs (x86) require GOT reg to be valid for external calls.
-
ok. this would make the PLT more directly analogous to the IAT then (ex: a stub used typically only on external calls)?...
-
meanwhile, assuming I make progress on the SH compiler; torn between GOT-for-everything and explicit PC-relative addressing.
-
PC relative only works for local, and only for non-fdpic.
-
yeah, it is a tradeoff; could possibly save some cycles for PIC and be limited to local calls (with vars/... still via GOT). TBD
-
I'm still not clear on why you'd want to write an arch-specific compiler rather than a modern backend...
-
I have most of the front-end from a prior C compiler; mine is small enough that it doesn't take a long time to recompile.
-
also LCC looked like it would be more effort overall to get what I want from it, and has a license I am not fond of.
- 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.