<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.arm.com/utility/feedstylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Forcing compiler to define functions in ECODE space</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/16269/forcing-compiler-to-define-functions-in-ecode-space</link><description> Hi everyone, 
 
I&amp;#39;m trying to force the CX51 compiler to put all the function from a specific module to ECODE memory space (to move it to external flash memory in future). But the compiler seems to apply some sort of optimization, i.e. it places some</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: Forcing compiler to define functions in ECODE space</title><link>https://community.arm.com/thread/95919?ContentTypeID=1</link><pubDate>Wed, 12 Nov 2003 09:17:42 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:7eb48e8e-e302-42ba-b866-a88b9b4a6e0e</guid><dc:creator>Ilia Lotosh</dc:creator><description>&lt;p&gt;No it&amp;#39;s not. When you generate ASM file from C source (the linker is not involved in this process) you can see segment allocation (not the absolute address, but a memory space)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Forcing compiler to define functions in ECODE space</title><link>https://community.arm.com/thread/86567?ContentTypeID=1</link><pubDate>Wed, 12 Nov 2003 09:11:21 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:35d6fec4-fd8c-4183-9533-86752fb16eec</guid><dc:creator>Andy Neil</dc:creator><description>&lt;p&gt;This is the Linker&amp;#39;s job - not the Compiler&amp;#39;s!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Forcing compiler to define functions in ECODE space</title><link>https://community.arm.com/thread/41251?ContentTypeID=1</link><pubDate>Wed, 12 Nov 2003 07:57:48 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:97bc21c0-84e3-4526-9427-e7b38b395db1</guid><dc:creator>Ilia Lotosh</dc:creator><description>&lt;p&gt;Ok, I found the solution. All I was need to do is eliminate all references to code and xdata memory spaces in the code I wanted to place in ECODE.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>