Texas Instruments TMS34010 User manual
TMS34010
C Compiler
User's Guide
."
TEXAS
INSTRUMENTS
SPVUOO5
TMS34010 C
Col11piler
User's Guide
TEXAS
INSTRUMENTS
IMPORTANT
NOTICE
Texas Instruments (TI) reserves the right
to
make changes in the devices or the
device specifications identified in this publication
without
notice.
TI
advises
its customers
to
obtain the latest version
of
device specifications
to
verify,
before placing orders, that the information being relied upon by the customer
is
current.
In the absence
of
written agreement
to
the contrary, TI assumes no liability for
TI applications assistance, customer's product design, or infringement
of
pat-
ents or copyrights
of
third parties
by
or arising from use
of
semiconductor
devices described herein. Nor does TI warrant or represent that any license,
either express or implied,
is
granted under any patent right, copyright. or other
intellectual property right
of
TI covering or relating
to
any combination, ma-
chine, or process in
which
such semiconductor devices might be or are used.
Copyright © 1986, Texas Instruments Incorporated
Contents
Section
1
1.1
1.2
TMS34010
C
Compiler
Package
Product
Overview
Applicable Documents
Documentation Conventions
Page
1-1
1-2
1-2
2
TMS34010
C
Compiler
Package
Installation
2-1
2.1
Installation for Texas Instruments and
IBM
PC
Systems
........
2-2
2.1.1 Hardware Requirements
..............
........
2-2
2.1.2 Installation for TIPC and
IBM
PC
Systems
with
Dual Diskette Drives
2-2
2.1.3 Installation for
PC
Systems
with
a Winchester Disk and Single Diskette
Drive
..............
2-3
2.1.4 Tools Verification on
PC
Systems
2-4
2.2
VAXNMS
Systems
2-6
2.2.1 Installation Procedure
.....
2-6
2.2.2 Tools Verification . . . . .
2-6
2.3 VAX/ULTRIX and
VAX/UNIX
System V
2-7
2.3.1 Instanation Procedure
.......
2-7
2.3.2 Tools Verification on ULTRIX and UNIX Systems
2-7
3
Invocation
and
Operation
of
the
TMS34010
C
Compiler
3-1
3.1
The TMS3401 0 C Preprocessor (GSPCPP)
3-2
3.1.1 Invoking GSPCPP
3-2
3.1.2 GSPCPP Options
.....
3-2
3.1.3 Operation
of
GSPCPP
3-3
3.2 The TMS3401 0 Parser (GSPCC)
3-3
3.2.1 Invoking the Parser
3-3
3.2.2 Operation
of
the Parser
3-4
3.3
,The
Code Generator (GSPCG)
3-4
3.3.1 Invoking GSPCG
3-4
3.3.2 GSPCG Options
3-5
3.3.3 Input Requirements
3-6
3.3.4 GSPCG Output
3-6
3.4 Batch Execution
of
the C Compiler
,3-6
3.5 Assembling a C Program
3-
7
3.6 Archiving a C Program
3-
7
3.7 Linking a C Program
3-7
3.7.1 Run-Time Initialization
3-7
3.7.2 Object Libraries and Run-Time Support
3-8
3.7.3 The
-c
Option
in
the Linker
3-8
3.7.4 Linker Command File
.........
3-8
iii
4
The
TMS34010
C
language
4-1
4.1
Identifiers and Keywords
4-2
4.2 Constants
4-2
4.3
TMS34010
C Data Types
4-2
4.3.1 Derived Types
4-3
4.4 Object Alignment
4-4
4.5 Conversions
4-4
4.6 Expressions
4-4
4.6.1 Void Expressions
4-4
4.6.2 Primary Expressions
4-5
4.6.3 Unary Operators in Expressions
4-5
4.6.4 Assignment Operators in Expressions
4-5
4.7 Declarations
4-5
4.7.1 Storage Class Specifiers
in
Declarations
4-5
4.7.2 Type Specifiers in Declarations
4-6
4.7.3 Structure and Union Declarations
4-6
4.7.4 Enumeration Declarations
4-7
4.8 Initialization
of
Static and Global Variables
4-8
4.9
8sm
Statement
4-8
4.10
Lexi~al
Scope Rules . .
..
4-10
5
TMS34010
C
Run-Time
Environment
5-1
5.1
Memory Model
5-2
5.1.1
TMS34010
C Stacks
5-2
5.1.2 Global Variable Memory Allocation
5-3
5.1.3 Structure Packing and Field Manipulation
5-3
5.1.4 Array Alignment
5-3
5.2 Register Conventions
5-4
5.2.1 D.edicated Registers
5-4
5.2.2 Using Registers
5-4
5.2.3 Register Variables
5-5
5.3 Integer Expression Analysis
5-5
5.4 Floating Point Conventions
5-6
5.5 Function Call Conventions
5-7
5.5.1 Register Usage Within Functions
5-8
5.5.2 Passing Parameters
5-8
5.5.3 Local Frame Generation
5-9
5.5.4 Function Termination
5-10
5.5.5 Restoration
of
the
CaUer's
Environment 5-11
5.5.6 Return from Function 5-11
5.6 Interrupt Handling 5-11
5.7 System Initialization
5-12
5.7.1 System Stack
5-13
5.7.2 Program Stack
5-13
5.7.3 Initialization
of
Global Variables
5-13
iv
6
6.1
6.1.1
6.2
6.3
6.4
A
8
C
D
E
TMS34010
Run-Time
Support
Memory
Management
...........
.
Specifying the Size
of
Memory
to
Manage
String Functions
............
.
Character Typing and Conversion Macros
Miscellaneous Functions
.......
.
Fatal
Errors
Reference
Documents
C Preprocessor
Directives
Floating
Point
Facility
Interfacing
Assembly Language
with
C
6-1
6-2
6-2
6-2
6-3
6-3
A-1
8-1
C-1
D-1
E-1
v
Illustrations
Figure Page
1
-1
.
TMS34010
C Compiler Package Interaction . . . . . . . . . . . . . . . . . . . . .
..
1-1
5-1 . Typical Function Call
with
Parameters
Passed,
No Value Returned
5-8
D-1. Single-Precision Floating Point Format . . . . . . . . . . . . . . . . . . . . . . . .
..
D-2
D-2. Double-Precision Floating Point Format . . . . . . . . . . . . . . . . . . . . . . . .
..
D-3
D-3. Single-Precision Normalization . . . . . . . . . . . . . . . . . . . . .
..
D-5
Tables
Table Page
4-1. TMS34010 C Data Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
..
4-3
D-1. Floating Point Error Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
..
D-7
vi
1.
TMS34010
C
Compiler
Package
Product
Overview
The C programming language has become one
of
the
dominant
languages
for
high-level graphics software. Thus, C
is
a logical choice
for
systems, periph-
eral, and applications software developers using the
TMS34010
Graphics
System Processor. GSP
C,
a compiler implementation for the TMS3401 0, has
been created
to
allow
developers
to
tap this software base
for
high-
performance
TMS34010
systems. GSP C accepts standard Kernighan and
Ritchie C source code and produces
TMS34010
assembly language source
code.
The TMS3401 0 C Compiler Package consists
of
a C Preprocessor, a Parser,
and a Code Generator,
as
well
as
Run-Time Support and Floating Point Li-
braries. The TMS3401 0 Assembly Language Package supports the assembly,
archiving,-and linking
of
compiler-generated software. The resulting execut-
able code can be run on a TMS3401 0 target system. Target systems can
in-
clude software simulators, software development boards, Texas Instruments
XDS (Extended Development Systems) units,
or
custom TMS3401 0 systems.
An illustration
of
this interaction
is
shown
in Figure
1-1.
1MS34010
FONTS
LIBRARY
1MS34010
MATH/GRAPHICS
FUNCTION
UBRARY
Figure
1-1.
TMS34010
C
Compiler
Package
Interaction
1-1
TMS34010
C
Compiler
Package
Product
Overview
1.1
Applicable
Documents
• Kernighan, B., and
D.
Ritchie.
The
C Programming Language, Pren-
tice-Hall, Englewood Cliffs,
New
Jersey, 1978.
• Kochan, Steve
G.
Programming in
C,
Hayden Book Company.
• Sobelman, Gerald
E.
and David
E.
Krekelberg.
Advanced
C:
Techniques
and
Applications, Que Corporation, 1985.
•
TMS34010
User's Guide (SPPU005), covering all the hardware related
subjects: architecture, registers, addressing modes, etc.
•
TMS34010
Assembly Language Tools User's Guide
(SPDU076),
cov-
ering the assembler, linker, archiver, and PROM programming utility.
•
TMS34010
Software Development Board User's Guide (SPVU002),
describing a PC-based
tool
for developing and debugging programs for
the TMS3401
O.
•
TMS34010
XDS/22
User's Guide
(SPDU058)
describing the most
powerful
tool
available
for
developing software
for
the TMS3401
O.
•
TMS34010
Font
Library User's Guide
(SPVU005),
describing the
font
data structure and illustrating each
of
the available fonts.
1.2
Documentation
Conventions
1-2
The documentation conventions used
in
this
book
include:
<>
Angle brackets enclose user-supplied information that
is
to be typed
out;
for
example,
<filename>
indicates
that
the name
of
the file is
to
be entered. The brackets themselves
are
not
entered, except
in
the case
of
#include
statements used in illustrating the syntax
of
some macros
(see Section 6, TMS3401 0 Run-Time Support).
[]
Square brackets enclose optional items.
A
special
fbnt
is
used
for
information displayed on the screen.
Underscoring
is
used
to
indicate the information you type
in
response
to
prompts or other screen displays.
Italics
are
used
to
highlight
function names, commands, code, and similar
items
within
a text line.
Boldface type is used
to
indicate emphasis.
In Section 4, text in the left margin gives references
to
corresponding sections
in Kernighan and Ritchie's book,
The
C Programming Language, or indicates
additional information
not
included in their book.
2.
TMS34010
C
Compiler
Package Installation
The TMS3401 0 C Compiler operates under these operating systems:
•
MS'
-DOS Version
2.1
(or
later)
• PC-DOS2 Version
2.1
(or later)
•
VAXNMS3
• VAX/ULTRIX™3
• VAX/UNIX™4 System V
MS-DOS
is
a trademark
of
Microsoft
Corporation.
2
PC-DOS
is
a trademark
of
International Business Machines.
3
VAX,
VMS,
and ULTRIX are trademarks
of
Digital Equipment Corporation.
4
UNIX
is
a trademark
of
AT&T
Bell Laboratories.
2-1
TMS34010
C
Compiler
Package
Installation
2.1
Installation
for
Texas
Instruments
and
IBM
PC
Systems
2.1.1
Hardware
Requirements
The TMS3401 0 C Compiler requires your system
to
be configured
with
512K
bytes
of
RAM.
It
is
also recommended that the system be configured
with
a
Winchester disk.
Note:
The
MS-
DOS/PC-DOS version
of
the
TMS34010
C compiler
is
distrib-
uted on
two
floppy
diskettes. The first step for the user is
to
make backup
copies
of
the software on blank diskettes. The backup diskettes should
be used in the system instead
of
the original diskettes. This
will
afford the
advantage
of
keeping the original copy free from accidental corruption.
2.1.2
Installation
for
TIPC
and
IBM
PC
Systems
with
Dual
Diskette
Drives
2-2
Warning:
Prior
to
proceeding,
make
sure
the
distribution
diskettes
have
write-protect
tabs
applied
to
prevent
the
risk
of
destroying
the
information
on
the
diskettes.
Use
the DISKCOPY command
to
back
up
the software package onto your
blank diskettes. Follow these steps
to
perform this backup:
1)
Insert the
MS-
DOS or PC-DOS system diskette in drive
A:.
2)
Enter:
DISKCOPY A:
B:/FIV
3) The DISKCOPY
function
prompts you
to
place the source diskette in
drive A:. Place one
of
the distribution diskettes in drive A:.
4)
You
are
now
prompted to place the destination diskette in drive
B:.
Place
a blank diskette in drive
B:.
The DISKCOPY function copies from the distribution diskette in drive
A:
to the blank diskette in drive
B:.
The
IF
option formats the destination
diskette before copying, precluding the possibility
of
directory errors on
the backup diskette. The
IV
option checks the diskette for media errors.
5) Repeat steps 2 through 5 for each distribution diskette.
TMS34010
C
Compiler
Package
Installation
2.1.3
Installation
for
PC
Systems
with
a
Winchester
Disk and
Single
Diskette
Drive
This procedure
is
for backup
of
the distribution diskettes on a second set
of
floppy
diskettes using a single
floppy
disk drive. Additionally, it
is
recom-
mended that the distribution diskettes be backed up on the Winchester,
both
for speed
of
access,
as
well
as
for
safety
of
the software.
MS-DOS
2.1
and PC-DOS
2.1
are
operating system versions that support a
hierarchical file system. For these systems
it
is
recommended that a subdirec-
tory
for
TMS3401 0 development tools be created.
Warning:
Prior
to
proceeding,
make
sure
the
distribution
diskettes
have
write-protect
tabs
applied
to
prevent
the
risk
of
destroying
the
information
on
the
diskettes.
To back up the distribution diskettes using the single
floppy
disk drive,
follow
these steps:
1)
Making sure that the
utility
function DISKCOPY.COM
is
available
for
execution, type:
DISKCOPY
A:
B:/F/V
2)
The DISKCOPY function prompts you to place the source diskette
in
drive
A.
Place one
of
the distribution diskettes
in
drive A:. The
DISKCOPY function accesses the disk to determine its type and format.
3)
You are then prompted to replace the source diskette in drive
A:
with
the
destination diskette. Place a blank diskette in drive
A:.
The
IF
option
of
the DISKCOPY function causes the destination diskette
to
be
formatted
before copying, precluding the possibility
of
directory errors on the
backup diskette. The IV
option
checks the diskette
for
media errors.
4)
After DISKCOPY formats the. backup diskette, it prompts you
to
switch
back and forth between the source and destination diskettes, copying
the distribution diskette
to
the backup diskette. After each distribution
diskette has been copied, DISKCOPY prompts you for more diskettes to
copy. Respond
YES
until all the distribution diskettes
are
copied.
If
you plan to place the TMS3401 0 software tools
in
a directory on the
Win-
. chester disk
as
recommended,
follow
these steps:
1)
Create a subdirectory
to
contain the
TMS34010
development tools by
typing:
MKDIR
\GSPTOOLS
2)
Make the
TMS34010
development tools directory the current directory
by typing:
CD \GSPTOOLS
2-3
TMS34010
C
Compiler
Package
Installation
3)
Place a distribution diskette in drive A:. Copy the contents
of
the
dis-
tribution diskette by typing:
COPY A:*.*
Li..
The IV
option
causes the system
to
verify that. after copying, the source
and the destination files
are
identical.
4)
Repeat step 3
for
each distribution diskette.
5)
Makj3 sure the directory you placed the tools in (in this example,
GSPTOOLS)
is
in the current pathway.
2.1.4
Tools
Verification
on PC Systems
2-4
When the TMS3401 0 development tools have been backed up
and/or
copied
onto
the Winchester disk, verify that your copies
are
executable. Use the batch
file GSPC.BAT provided in the package
for
this verification. This batch file
first calls the C preprocessor (GSPCPP), then the parser (GSPCC), the code
generator next (GSPCG), and finally the assembler (GSPA). The result
is
linkable object code. When using this batch file, remember that you must have
installed the
TMS34010
Assembly Language Package on your system; this
package includes the assembler (GSPA), the linker (GSPLNK), the simulator
(GSPSIM).
and the archiver (GSPAR).
1)
To verify that the compiler
is
properly installed, invoke GSPC.BAT
to
compile the file TESTC34.C
by
typing:
GSPC TESTC34
2)
The batch file responds
with:
---[TESTC34]---
C
Pre-Processor,
<version
number>
©
Copyright
1985,
1986
Texas
Instruments
Inc.
GSP
C
Compiler,
<version
number>
©
Copyright
1985,
1986
Texas
Instruments
Inc.
"TESTC34.C":
~~>
MAIN
GSP
C
Codegen,
<version
number>
©
Copyright
1985,
1986
Texas
Instruments
Inc.
"TESTC34.C":
~~>
MAIN
GSP
COFF
Assembler,
<version
number>
©
Copyright
1985,
1986
Texas
Instruments
Inc.
PASS
1
PASS
1.1
ON
SECTION
.text
PASS
2 .
No
Errors,
No
Warnings
3)
Verify the operation
of
the
TMS34010
linker. The link command file
TESTC34.CMD
is
included in the package
for
linking the
output
of
the
compiler and assembler together
with
the runtime support (RTS.LlB)
and floating
point
(FLlB.LlB)
libraries. Type:
GSPLNK TESTC34.CMD
TMS34010
C
Compiler
Package
Installation
The
TMS3401
0 linker responds with:
GSP
COFF
Linker,
<version
number>
©
Copyright
1985,
1986
Texas
Instruments,
Inc.
where <version number>
is
the version number of the current
TMS34010
linker.
4)
Continue verification of the
TMS3401
0 development tools
by
invoking
the
TMS3401
0 simulator. Type:
GSPSIM
TESTC34
The
TMS34010
simulator responds by loading the linked output
TESTC34.0UT
and displaying the register file and status information.
After the simulator's display
has
been placed
on
the screen,
run
the
linked output by typing:
RUN
<return>
The simulator responds by displaying:
YOU'RE
OK,
WE'RE
OK!!!
in
white letters
in
the
center
of the scratch display area. Exit the simu-
lator by typing:
Q*
<return>
5)
Conclude the verification
session
by
testing the object/source archiver.
Type:
GSPAR!
RTS.L1B
The archiver responds by giving a table of contents for the runtime sup-
port library, similar to the following:
GSP
Archiver
<version
number>
©
Copyright
1985,
1986
Texas
Instruments,
Inc.
FILE
NAME
SIZE
DATE
atof.obj
1216
Tue
Aug 12
00
01
04
1986
atoi.obj
450
Tue
Aug
12
00
01
04
1986
boot.obj
572
Tue
Aug
12
00
01
04
1986
ctype.obj
464
Tue
Aug
12
00
01
04
1986
Itoa.obj
424
Tue
Aug
12
00
01
04
1986
memory.obj
1874
Tue
Aug 12
00
01
04
1986
movmem.obj
382
Tue
Aug 12
00
01
04
1986
printf.obj
878
Tue
Aug
12
00 01
04
1986
strcat.obj
358
Tue
Aug
12
00
01
04
1986
strchr.obj
352
Tue
Aug
12
00
01
04
1986
strcmp.obj
360
Tue
Aug
12
00
01 04
1986
strcpy.obj
350
Tue
Aug
12
00
01
04
1986
strlen.obj
340
Tue
Aug
12
00 01
04
1986
strncat.obj
374
Tue
Aug
12
00
01
04
1986
strncmp.obj
376
Tue
Aug
12
00
01 04
1986
strncpy.obj
372
Tue
Aug
12
00
01
04
1986
strrchr.obj
352
Tue
Aug
12
00
01
04
1986
fconvert.obj
342
Tue
Aug
12
00 01
04
1986
setjmp.obj
332
Tue
Aug 12
00
01 04
1986
2-5
TMS34010
C
Compiler
Package
Installation
2.2
VAX/VMS
Systems
The tape provided was made at
1600
BPI using the
VMS
BACKUP utility.
Follow the instructions in this section
to
install and
verify
the tools contained
on the tape.
2.2.1
Installation
Procedure
1)
Mount
the tape on your tape drive.
2)
Execute the
following
VMS
commands. Note
that
you must create a
destination directory in
which
to
put the tools. This example uses
DEST:<dest-directory> to indicate the destination. TAPE:
is
to
be re-
placed
with
the name
of
the tape drive being used in the backup proce-
dure.
$
allocate
$
init/den;1600
$
mount/for
$
backup
$
dismount
$
dealloc
TAPE:
TAPE:gspc
TAPE:
TAPE:gspc.bck
DEST:<dest-directory>
TAPE:
TAPE:
3)
The product tape contains a command file called setup.com. This file
is
used to set up
VMS
symbols that
allow
the tools
to
be executed
in
the
same manner
as
any other command. This command file must be run
as
follows:
$
@setup
DEST:<dest-directory>
This sets
up
symbols to be used to call the various tools. The symbols
defined
are
listed on the screen by the command file.
2.2.2
Tools
Verification
2-6
The product tape contains a test file (testc34.c) that can
be
compiled and
compared
with
testc34.cmp
to
ensure that the C compiler has been installed
correctly and
is
functioning.
For example, enter:
$
gspcpp
testc34
$
gspcc
testc34
$
gspcg
-*
testc34
This produces
an
assembly language file testc34.asm,
which
should
be
exactly
like the file testc34.cmp shipped on the product tape.
TMS34010
C
Compiler
Package
Installation
2,3
VAX/ULTRIX
and
VAX/UNIX
System
V
The tape provided was made at
1600
BPI using the
tar
utility. This section
instructs you in installing and verifying the tools contained on the tape.
2,3,1
Installation
Procedure
1)
Mount
the tape on your tape drive.
2) Make the current directory the directory into
which
the tools
will
be re-
stored.
3) Enter the
tar
command appropriate for your system;
for
example:
tar~
This copies the entire tape
into
the current directory.
2,3,2
Tools
Verification
on
ULTRIX
and
UNIX
Systems
The product tape contains a test file (testc34.c) that can be compiled
to
en-
sure that the
working
C compiler has been installed. The tape contains the
correct
output
file
to
compare
to
the file created during the test.
For example, enter:
9MlQQQ testc34
~
testc34
~
.:l:testc34
This creates the assembly file testc34.asm,
which
can be compared
to
the
testc34.cmp file shipped on the tape.
2-7
TMS34010
C
Compiler
Package
Installation
2-8
3.
Invocation
and
Operation
of
the
TMS3401
0 C
Compiler
The TMS3401 0 C compiler consists
of
three parts:
• Preprocessor (GSPCPP)
• Parser (GSPCC)
• Code generator (GSPCG)
The
output
of
the code generator must be assembled
with
the
TMS34010
COFF
(common
object file format) assembler and linked
with
TMS34010
C
Run-Time
Support
using the COFF linker
(GSPLNK)
to
produce executable
object
code. Refer
to
the
TMS34010
User's Guide and
UNIX
COFF
doc-
umentation for details
of
the
object file format.
Note:
Each
of
the tools discussed here has
options
available for use in the
in-
vocation (command) line. These
options
are unique among themselves
and must be used
as
shown
herein.
Any
other items included in the
in-
vocation may
be
ignored or may cause errors.
3-1
Invocation
and
Operation
of
the
TMS34010
C
Compiler
3.1
The
TMS34010
C
Preprocessor
(GSPCPP)
The C preprocessor, GSPCPP,
is
invoked
as
the first
pass
of
the TMS3401 0
C compiler. GSPCPP handles macro definitions and substitutions, #include
files, line number directives, and conditional compilation. The preprocessor
requires the original C source file
as
input and produces
as
output
a modified
source file suitable for input
to
GSPCC.
This preprocessor
is
the
same
preprocessor described in
The
C Programming
Language, by
B.
Kernighan and
D.
Ritchie (referred to hereafter
as
K&R).
Additional information
can
be
found in that book.
3.1.1
Invoking
GSPCPP
The preprocessor begins execution when the
following
command
is
entered:
where:
input
file
output
file
options
.9.2.I2.£E£
[input
file]
[output
file]
[option's]
is
the name
of
the C source file used
as
the input file.
If
no
extension
is
given,
an
extension
of
.c
is
assumed.
If
no input
file
is
given, a prompt appears.
is
the name
of
the file
output
by GSPCPP. The
output
file
can
be
omitted, in
which
case
the name given
to
the
out-
put-file defaults
to
the
input-file
name
with
an
extension
of
.cpp.
lists any
of
the available GSPCPP options (see Section
3.1.3). The options parameter can appear anywhere in the
invocation line and can be used multiple times.
3.1.2
GSPCPP
Options
3-2
GSPCPP's options
are
case-sensitive,
single-letter fields prefixed
by
hy-
phens
(-).
Some options have additional fields,
which
immediately
follow
the
option letter
with
no
intervening
spaces. The following list describes
op-
tions available; each option
is
uppercase.
-p
Tells the preprocessor
not
to produce the line number and
file :i3-P information used by the compiler. The compila-
tion is otherwise the same
as
if
this information were
produced.
-C
Copies comments to the
output
file. Otherwise, GSPCPP
strips comments.
-D<name>=def
Defines name
as
if
the
following
line appeared at the
top
of
the input file:
#define
name
def
The symbol name is then recognized for
#if
and
#ifdef
statements,
without
having been explicitly defined in the
text
of
the program.
Invocation
and
Operation
of
the
TMS34010
C
Compiler
-I<dir>
The
=del
can be omitted, in
which
case name is defined
to
the value 1.
This
option
can be used multiple times
for
defining
mul-
tiple names
by
separating the
-D
options
by
spaces.
(Uppercase i) Adds dir to the list
of
directories
to
be
searched for #include files. Omitting
dir
causes
option
-I
to be ignored. This option can
be
used mUltiple times,
each one separated by a space,
to
search more directories.
3.1.3
Operation
of
GSPCPP
GSPCPP maintains and recognizes the name -
-LlNE-
-
as
the current
line number
(a
decimal integer) and the name -
-FILE-
-
as
the current
file name
(a
C string). Note
that
these names begin
with
two
underscore
characters and end
with
two
underscore characters
with
no
spaces
be-
tween
the
characters.
You can use these names in the same
way
as
any
other defined name,
including
using them in macros.
All
GSPCPP directives begin
with
the character
#,
which
must appear in
col-
umn 1.
Any
number
of
blanks and tabs are allowed between # and the
di-
rective name. The directives are described in Appendix
C,
and additional
information can be
found
in K&R.
The error messages produced
by
the preprocessor are self-explanatory; the line
number and the filename where the error occurred are printed along
with
the
diagnostic.
3.2
The
TMS34010
Parser
(GSPCC)
The parser, GSPCC, is the second pass
of
the C compiler.
It
reads
the
output
of
GSPCPP (the preprocessor), parses
it
perfo.rms syntax checking, and writes
an
intermediate file
for
input
to
the code generator (GSPCG).
3.2.1
Invoking
the
Parser
The parser
is
invoked
with
the
command:
~
[input
filel
[output
filel
1:.ll
where:
input
file
output
file
-z
is the name
of
the
input
file. The default extension
for
the
input
file
is
.cpp
if
none
is
specified.
If
no
input
file is given,
a
prompt
appears.
is
the name
of
the
output
file. This is
the
intermediate file
used
as
input
to
the GSPCG.
If
this argument is omitted, the
intermediate file is given the same name
as
the
input
file
with
the default extension .il.
is the
option
which
retains the
.cpp
input
file. The
.cpp
file
is
deleted
if
-z
is
not
specified. This parameter can be
placed anywhere in the invocation line.
3-3
Other manuals for TMS34010
1
Table of contents
Other Texas Instruments Computer Hardware manuals
Texas Instruments
Texas Instruments MSP430FR5739 User manual
Texas Instruments
Texas Instruments TPS7A15 User manual
Texas Instruments
Texas Instruments C28 Series User manual
Texas Instruments
Texas Instruments Sitara AM1335 Series User manual
Texas Instruments
Texas Instruments TMS320C80 User manual
Texas Instruments
Texas Instruments CC3100 SimpleLink User manual
Texas Instruments
Texas Instruments OMAP36 Series Product manual
Texas Instruments
Texas Instruments EZShunt INA740 User manual
Texas Instruments
Texas Instruments AM62A7 Guide
Texas Instruments
Texas Instruments LMG342XEVM-04X User manual
Texas Instruments
Texas Instruments TPS65941213-Q1 User manual
Texas Instruments
Texas Instruments Motor Control User manual
Texas Instruments
Texas Instruments TS3USB3031 User manual
Texas Instruments
Texas Instruments PCI7620 User manual
Texas Instruments
Texas Instruments MSP-EXP430F5438 User manual
Texas Instruments
Texas Instruments DS10 Operating instructions
Texas Instruments
Texas Instruments SimpleLink CC1312PSIP User manual
Texas Instruments
Texas Instruments DRV603EVM User manual
Texas Instruments
Texas Instruments CapTIvate Touch Parts list manual
Texas Instruments
Texas Instruments TMS320F2837 D Series User manual
Popular Computer Hardware manuals by other brands
Madrigal Audio
Madrigal Audio Mark Levinson 39 operating manual
Tech tools
Tech tools EconoROM III user manual
ICP vortex Corporation
ICP vortex Corporation 32-Bit 66MHz low profile PCI Wide/Ultra160... specification
Pico Macom
Pico Macom CHC16U/550 Installation and operation manual
Sparklan
Sparklan WUBR-502GN user manual
Siemens
Siemens SIMATIC NET CP 5613 A2 operating instructions
