<?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>about error L107: address overflow</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/31556/about-error-l107-address-overflow</link><description> Now I compile my program and counter one error.which is: 
ERROR L107:ADDRESS SPACE OVERFLOW 
SPACE: DATA 
SEGMENT:_DATA_GROUP_ 
LENGTH: 006EH 
I can compile it if I select the memory model of compact or large,but the small model will counter above linker</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: about error L107: address overflow</title><link>https://community.arm.com/thread/39030?ContentTypeID=1</link><pubDate>Fri, 09 Aug 2002 08:46:56 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:620342e8-54a5-489b-9892-38cdccbf24b0</guid><dc:creator>Jon Ward</dc:creator><description>&lt;p&gt;Take a look at the following knowledgebase article.&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://www.keil.com/support/docs/1241.htm"&gt;http://www.keil.com/support/docs/1241.htm&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Jon&lt;/b&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: about error L107: address overflow</title><link>https://community.arm.com/thread/39028?ContentTypeID=1</link><pubDate>Fri, 09 Aug 2002 07:59:30 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:f996ee20-0f7c-44c6-83ce-5dfa55106edb</guid><dc:creator>Mark Odell</dc:creator><description>&lt;p&gt;Turn optimization on to full, e.g. OT(9, SIZE). Next, declare storage for &lt;b&gt;every&lt;/b&gt; variable. Every one. E.g. for arrays, put them in xdata or idata if you don&amp;#39;t have any xdata. For small varaibles that have to be fast, put them in data. For variables that get accessed rarely put them in xdata. Any const variables should be declared in code, otherwise they go in the default memory space (DATA for the small model) as do all variables not given an explicit storage type. &lt;br /&gt;
&lt;br /&gt;
See my UART driver for an example of using code, data, idata, and xdata storage qualifiers. It&amp;#39;s free at &lt;a href="http://www.embeddedfw.com" target="_blank"&gt;http://www.embeddedfw.com&lt;/a&gt; (link at bottom of page) and it was built with the small memory model.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>