mirror of
https://github.com/cc65/cc65.git
synced 2025-01-22 21:32:57 +00:00
Update for new version
git-svn-id: svn://svn.cc65.org/cc65/trunk@105 b7a2c559-68d2-44c3-8de9-860c34a00d81
This commit is contained in:
parent
5453c45d8f
commit
6fb18bf469
@ -112,7 +112,7 @@ compiling them into assembler. Therefore if you have a C function named
|
||||
Systems:
|
||||
--------
|
||||
|
||||
Supported systems at this time are: C64, C128, Plus/4, CBM 600/700, the newer
|
||||
Supported systems at this time are: C64, C128, Plus/4, CBM 600/700, the newer
|
||||
PET machines (not 2001), and the Apple ][ (thanks to Kevin Ruland, who did the
|
||||
port).
|
||||
|
||||
@ -141,6 +141,7 @@ PET: The startup code will adjust the upper memory limit to the installed
|
||||
APPLE2: The program starts at $800, and of RAM is $8E00, so 33.5K of memory
|
||||
(including stack) are available.
|
||||
|
||||
|
||||
Note: The above numbers do not mean that the remaining memory is unusable.
|
||||
However, it is not linear memory and must be accessed by other, nonportable
|
||||
methods. I'm thinking about a library extension that allows access to the
|
||||
@ -162,6 +163,9 @@ Example, insert a break instruction into the code:
|
||||
Note: The \t in the string is replaced by the tab character, as in all other
|
||||
strings.
|
||||
|
||||
Beware: Be careful when inserting inline code since this may collide with
|
||||
the work of the optimizer.
|
||||
|
||||
|
||||
|
||||
Pseudo variables:
|
||||
@ -176,10 +180,7 @@ functions results and pass parameters.
|
||||
This feature is useful with inline assembly and macros. For example, a macro
|
||||
that reads a CRTC register may be written like this:
|
||||
|
||||
#define wr(idx) (__AX__=(idx),asm("\tsta\t$2000\n\tlda\t$2000\n\tldx\t#$00"),__AX__)
|
||||
|
||||
An obvious problem here is that macro definitions may not use more than one
|
||||
line.
|
||||
|
||||
|
||||
#define wr(idx) (__AX__=(idx), \
|
||||
asm("\tsta\t$2000\n\tlda\t$2000\n\tldx\t#$00"), \
|
||||
__AX__)
|
||||
|
||||
|
@ -58,6 +58,10 @@ text.s:
|
||||
_text: .asciiz "Hello world!"
|
||||
|
||||
|
||||
(The example is rather stupid, since the text in text.s does not use the
|
||||
correct character set for the target machine - conversion is usually done
|
||||
by the compiler. However, we will ignore that here.)
|
||||
|
||||
We assume that the target file should be named "hello", and the target
|
||||
system is the C64.
|
||||
|
||||
@ -203,4 +207,4 @@ For more information about the compile & link utility see cl65.txt.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -168,7 +168,7 @@ The header files contain
|
||||
|
||||
|
||||
5. Direct console I/O - conio.h
|
||||
-------------------------------
|
||||
-------------------------------
|
||||
|
||||
The conio header file contains a large set of functions that do screen and
|
||||
keyboard I/O. The functions will write directly to the screen or poll the
|
||||
@ -183,6 +183,7 @@ targets:
|
||||
cbm610 (that is, the complete 600/700 series)
|
||||
pet (all PETs except the 2001)
|
||||
apple 2
|
||||
atari
|
||||
|
||||
The conio.h header file does also include the system specific header files
|
||||
which define constants for special characters and keys.
|
||||
|
@ -2,9 +2,11 @@
|
||||
Documentation overview:
|
||||
|
||||
|
||||
ar65.txt - Describes the ar65 archiver.
|
||||
BUGS - Known compiler bugs
|
||||
|
||||
debugging.txt - Debug programs using the VICE emulator.
|
||||
CREDITS - Who helped with the compiler and tools?
|
||||
|
||||
ar65.txt - Describes the ar65 archiver.
|
||||
|
||||
ca65.txt - Describes the ca65 macro assembler.
|
||||
|
||||
@ -15,6 +17,12 @@ Documentation overview:
|
||||
coding.txt - Containes hints on creating the most effective code
|
||||
with cc65.
|
||||
|
||||
compile.txt - How to compile cc65 and the support tools.
|
||||
|
||||
debugging.txt - Debug programs using the VICE emulator.
|
||||
|
||||
internal.doc - A somewhat older text describing several cc65 internals.
|
||||
|
||||
intro.txt - Describes the use of the tools by a short "hello world"
|
||||
example.
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user