<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On May 5, 2015, at 6:47 PM, Daniel Dilts <<a href="mailto:diltsman@gmail.com" class="">diltsman@gmail.com</a>> wrote:<br class=""><div><blockquote type="cite" class="">Take a look at how debuggers have migrated through the years. They too<br class=""><div class=""><div dir="ltr" class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
used to have their own script format. Now most (all?) popular debuggers<br class="">
do scripting through embedding an actual programming language. This<br class="">
could be a better way forward for linkers as well -- embed Python in the<br class="">
linker, define a Python API for linkable item placement, entry point,<br class="">
symbol operations, etc..., and then you also have the rest of Python at<br class="">
your fingertips.</blockquote><div class=""><br class=""></div><div class="">I mostly care about specifying address where specific symbols will be placed and specifying the memory layout of the platform. I normally use __attribute__((section(""))) to place the symbols in their own sections and then use the linker script to place the sections at the required addresses. How would this be accomplished without linker scripts?</div></div></div></div></blockquote><br class=""></div><div>I’d prefer to use an "__attribute__((address(0x1234)))” myself. That way you can control platform specifics with #ifdefs.</div><div><br class=""></div><div>-Chris</div><br class=""></body></html>