06.02.2013 Views

C166/ST10 Cross-Assembler, Linker/Locator, Utilities ... - Tasking

C166/ST10 Cross-Assembler, Linker/Locator, Utilities ... - Tasking

C166/ST10 Cross-Assembler, Linker/Locator, Utilities ... - Tasking

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

• • • • • • • •<br />

<strong>Linker</strong>/<strong>Locator</strong> 9−113<br />

the same effect was obtained if the next line was included at the end of<br />

the section STACKSECT:<br />

ORG $ − 20h<br />

Another example:<br />

like:<br />

SECSIZE( STACKSECT( 1024 ) )<br />

ORG 1024<br />

where STACKSECT is a relocatable section.<br />

Using the module scope switch in the SECSIZE control is allowed at the<br />

following syntactical locations:<br />

SECSIZE( {module−name size−control },... )<br />

When the module scope is general the SECSIZE control is applied to all<br />

sections with section−name and class−name.<br />

When the SECSIZE control is specified after the GENERAL control, all input<br />

modules are searched for the named sections. When multiple sections<br />

occur with the same name, only the first occurrence is resized. When all<br />

occurrences should be resized, the section name should be specified for<br />

each module (using the module scope switch) for all these sections. For<br />

example:<br />

GENERAL<br />

SECSIZE( { module1.obj SOMESECT ( 200h ) }<br />

{ module2.obj SOMESECT ( 200h ) } )<br />

Examples:<br />

secsize( Sec1 (1000))<br />

ss( Sec1 ’Class1’ (0F00H)) ss( Sec1 (+100))

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!