Thread: Z80 Compiler (for Ti)

I know there was some thread about it way back, but I don't know how much information could be salved from it.
Just looking to see if there's a nice C/C++ compiler for Z80. There should be, right?
So does anyone know anything? It's unfuriating to type BASIC on the calc itself, not to mention that it actually crawls.

Any tips would be appreciated.

I'm pretty sure IAR has a Z80 compiler. However, C++ for 8/16-bit processors tend to be beyond what you can expect to find - consider that you only have a maximum of 64KB of addressable memory at any given time, so code and data can't realistically be that big.

--
Mats

I almost expected C++ wouldn't work, but will do fine in this case, then. I'll check it out and see if I can find a compiler. Thanks.
(Although, I can't seem to find any download for the Z80 IDE/compiler on the site...)

http://www.iar.com/website1/1.0.1.0/330/1/index.php

--
Mats

http://www.ticalc.org/programming/ ?

Originally Posted by Elysia

Then if someone can suggest anything better except for Dev-C++/GCC or whatever it was, then I'll happily listen.

Did you look into tigcc?

Originally Posted by Dave_Sinkula

http://www.ticalc.org/programming/ ?

Originally Posted by Elysia

I can't even figure out what the resulting linked file is and what the Ti actually accepts.

It looked like you were trying to build an Intel hex file that you were calling it an .exe.

sdcc.exe --out-fmt-ihx -mz80 --profile --verbose --debug --out-fmt-ihx -mz80 --profile --verbose --stack-auto --debug -ID:\Program\SDCC\include -c main.c -o obj\Debug\main.rel
sdcc: Calling preprocessor...
sdcc: Generating code...
sdcc: Calling assembler...
sdcc.exe -LD:\Program\SDCC\lib -o bin\Debug\Test.exe --out-fmt-ihx -mz80 --profile --verbose --debug --out-fmt-ihx -mz80 --profile --verbose --stack-auto --debug obj\Debug\main.rel
obj\Debug\main.o: cannot open.
sdcc: Calling linker...
sdcc: Calling linker...
Process terminated with status 1 (0 minutes, 0 seconds)
0 errors, 0 warnings

I though this was saying to compile the .c into a .rel, and then link the .rel into an ".exe", and having no errors or warnings.

I would normally expect some .a type of file output from the linker which is then later translated into a .hex file for use with programming into the calculator. But then I'm not familiar with your system.

Originally Posted by Dave_Sinkula

Did you look into tigcc?

Nope, but I will. It looks interesting. Thanks.

It looked like you were trying to build an Intel hex file that you were calling it an .exe.
I though this was saying to compile the .c into a .rel, and then link the .rel into an ".exe", and having no errors or warnings.

I would normally expect some .a type of file output from the linker which is then later translated into a .hex file for use with programming into the calculator. But then I'm not familiar with your system.

Well, as I mentioned, since there's no documentation on the thing, I'm stabbing in the dark. Checking or unchecking the thing has no effect. The problem is that Code::Blocks doesn't supply the full path to the compiler.

Originally Posted by matsp

http://www.iar.com/website1/1.0.1.0/330/1/index.php

--
Mats

I found that, too, but there doesn't seem to be any download link.

Originally Posted by Elysia

I found that, too, but there doesn't seem to be any download link.

I'd contact them and ask if you can have a demo license for that.

--
Mats

Yep, seems to be the only way.

Awesome! Debugger, as well. Good tip! Excellent! Thanks!

I was the author of the old thread on this subject, never really did get it working. Although i was using the same compiler as jake123 suggested. Elysia, please let me know if you get it working

I don't know how to set up Code::Blocks to compile properly with it. It seems to complain in the linker.

Compiling: main.c
sdcc: Calling preprocessor...
sdcc: Generating code...
sdcc: Calling assembler...
Linking console executable: bin\Debug\Test.exe
obj\Debug\main.o: cannot open.
sdcc: Calling linker...
sdcc: Calling linker...
Process terminated with status 1 (0 minutes, 0 seconds)
0 errors, 0 warnings

Perhaps building on the command line will show you what's going on [yes, that's very old-fashioned, but sometimes the old-and-tried methods work better].

--
Mats