s5u1c33000c Epson Electronics America, Inc., s5u1c33000c Datasheet - Page 225

• Manufacturer Part Number: s5u1c33000c
• Description: Cmos 32-bit Single Chip Microcomputer S5u1c33000c Manual
• Manufacturer: Epson Electronics America, Inc.

-v3 command
Format:
Sample description: -v3
Explanation:
Default:
Note:
-codeblock command
Format:
Sample description: -codeblock MAIN_OBJ {main.o test.o}
Explanation:
Default:
Note:
S5U1C33000C MANUAL
(C COMPILER PACKAGE FOR S1C33 FAMILY) (Ver. 4)
-v3
Unless this command is specified, the file is processed as a Ver. 2.1 command file. The
above Ver. 3.0 commands are disabled, so that specifying any of those commands results in
an error.
Always be sure to specify the -v3 command in the first line of the command file. Not
specifying this command in the first line results in an error.
-codeblock <Block name> {<File name ... <File name>}
Unless specified using this command, all CODE sections in the object files are located in a
block named DEFAULT_CODE.
Specify this command when using the linker commands of lk33 Ver. 3.0 or later
versions.
In Ver. 3.0 mode, the following commands are enabled:
-codeblock, -datablock, -bssblock, -ucodeblock, -udatablock, -ubssblock, -addr, -defaddr
The following commands are disabled, so that specifying any of these commands results
in an error.
-code, -data, -bss, -ucode, -udata, -ubss, -section
The commands listed below can be used in the same way as with the conventional linker
commands.
-c, -m, -s, -cref, -g, -e, -w, -l, -o, -defsym, -d, -objsym, -ld, -inclink
This command combines the CODE sections included in the relocatable object files
specified in { } to create a new block.
The CODE sections are located at successive locations in this block in the specified
order.
At least one space or tab is required between -codeblock and <block name>.
When specifying multiple files, be sure to enter at least one space, tab, or line feed
between <file name> entries.
File names in { } can be written in two or more separate lines.
Example) -codeblock MAIN_OBJ
Up to 256 blocks can be defined.
A block name can contain up to 130 characters and are case-sensitive.
An object file name can contain up to 256 characters, including the path.
Up to 4,000 files can be specified in { }.
Defining two or more blocks with the same block name results in a warning.
In that case, the first block defined is effective
Example) -codeblock OBJ1 {test1.o test2.o}
Block names cannot be preceded by the symbol '@' or '#'.
No object file names that are the same can be specified in { } (except when they have
different paths).
At least one object file must be specified in { }.
If any file name specified in { } does not match the link file (including the path), a
warning is given and the file is processed as being not specified. If this results in no
valid files being specified in { }, an error results. However, this does not apply when
library objects are specified (i.e., "xxx.lib:xxx.o" is specified).
{
}
-codeblock OBJ1 {test3.o test4.o}
boot.o
main.o
sub.o
EPSON
(Link processing in lk33 Ver. 3.0)
... Effective
... Has no effect
CHAPTER 12: LINKER
209