_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!

I though that there was a set of standard functions like Mandelbrot calculations, or sorting algorythms, or things like that, that could be programmed in a standard C code, not specific to an architecture or compiler. And then fed to the compilers to see what code they do spit out.

I mean...



Is almost universally understood by every BASIC out there, but when compiled to machine code, there are differences between not only architectures but also compilers, aren't them?

Well, I did spend my evening implementing Tetris for my system in C. I didn't consciously do anything to tailor it to the WDC compiler so it might be a good candidate to see how easily I can build the same code with cc65 or vbcc.

Mandelbrot was discussed here: viewtopic.php?f=1&t=6323

The result is tied too much to output speed.

There was fib and tarai, thought not everyone wants or needs recursion: viewtopic.php?p=78840#p78840


My BASIC compiler generates this:

The total binary file size is under 200 bytes.

Yes, I have seen 6502 C benchmarks using mandelbrot, md5, or dhrystones. However, those are very small and the results are often dominated by the implmentation of a single feature or optimization. E.g. a mandelbrot calculation on the 6502 will mainly test the math libraries used. The dhrystone benchmark was intended to test a mixture of features considered typical use at that time. However, with modern compilers, it emphasizes a few specific optimizations that have far less impact in practice. So you may get hugely varying results using only one or two small tests.

So, if a comprehensive test suite is required, you probably want more and bigger tests. Those, however, are more likely to not work out of the box with all 6502 compilers due to different limitations of either the 6502 or the compilers. So you may have to pick and adapt, i.e. some work.

As another poster mentioned, if you are just choosing a compiler for your project, the best option probably is to test some of that code.


Yes, but that test will probably not be a good indication of how the compilers will translate e.g. a mandelbrot calculation.

This

was used to make a point, not to be taken as a real compiler test.

I'm reading comments about how to write code tailored for this or that compiler, and what I'm talking about is to create code that would stick to standard C (hence the BASIC example), and then leave up to the compilers how to make assembler from it.

That's why I talked about standard operations like the Mandelbrot stuff, or sorting stuff, or working with arrays... you name it! Those operations would be written in the most standard C (instead of tailored for cc65, vbc, WDC, or what ever) and fed to the compilers.

Then, things like code size and time of the operations the code is written to do would help to know which compiler is best in overall or in certain areas.

Compiler tests which spring to mind, all of which seem to have the property of creating an executable with some kind of function:
- compile a Basic or Logo interpreter
- compile a screen editor
- compile a program like Xmodem
- compile a FAT filesystem
- compile a TCP/IP stack
- compile a compiler

But of course, just blinking an LED or reading a temperature sensor are also in there. Something you might want to do with your '02 system.

All of these things have in common a need to perform I/O, which is going to be somewhat platform-specific.

Edit: I seem to be answering the question "Is this compiler useful" rather than "Which compiler is best" and I think I'm happy with that.

Here is someone who is comparing compilers...

https://bestofcpp.com/repo/sgadrat-6502-compilers-bench

Guilty as charged...

viewtopic.php?p=79347#p79347

Uh-oh. It is true, then...

_________________
In theory, there is no difference between theory and practice. In practice, there is. ...Jan van de Snepscheut

Has anybody else had the WDC compiler just crash when there's an error of any kind in your C code? Mine prints out the offending line but then segfaults leaving the reason as an exercise for the reader.

Andrew had been working on this compiler with WDC before his passing.

Does anybody know what he had accomplished and whether his changes are in the latest official version?

Hi

I have just started my journey down the 6502 road, or perhaps continuing where I left off back in the 80's.
I started with an "Aloha 66" clone of an Apple 2. Unfortunately I no longer have any of the gear that I collected back in the day.

I am currently looking at the WDC compiler.
I am a (Electronics Engineer) embedded C programmer and not really that keen to go back to assembler if I can help it. (though I think assembler it may be)

Tide is a waste of time. I thought it would be something like AVR studio....IDE as in "Integrated Development Environment"....as in editor.
It can call an external editor...that's about it.
If I try to change anything in options I get an Error message "Failed to set data for 'Version'" ...don't know what this means.
Though, when I finally exit options and come back in the changes are there. I had other problems too.
I would not bother with Tide, seems buggy.
(If I supplied software like this to a customer I would be out of business)

After finding the startup.asm files in your posts, (Thanks)
I have managed to compile a simple program for example,

unsigned char x, y;
void main(void)
{
y = 100;
for(x=0;x<10;x++)
{
y++;
}
while(1);
}

Error reporting is rudimentary. For example drop the semi-colon at Y=100 above and you get

WDC 65C02 C Version 3.49.1 Feb 6 2006 16:25:18
Copyright 1992-2006 by The Western Design Center, Inc.
for(x=0;x<10;x++)

So the problem is possibly on or above this line....but we can't tell you any more.

I then add these lines and re-compile

#include "stdio.h"
char WrkSpc[20];
sprintf(WrkSpc,"HELLO WORLD");

WDC 65C816 Linker Version 3.49.1 Apr 24 2006 15:40:38
Copyright (C) 1992-2006 The Western Design Center, Inc.
Undefined symbol: _unlink
Undefined symbol: _close
Undefined symbol: _isatty
Undefined symbol: _write
Undefined symbol: _lseek

Now, the documentation (https://www.wdc65xx.com/wdc/documentati ... Linker.pdf) mentions in CHAPTER 7 WDCLN (LINKER)
that
Note: There are calls to user defined functions that are system dependent.
Example: _unlink, _ _close, _ _isatty,_ _write, _ _lseek, _ _fseek.
_ _read, _ _open, _ _creat, _ _ access (see WDC_SDS/INCLUDE/FCNTL.H

So I guess I need to write some code to perform these functions or maybe do nothing.
I don't see how sprintf uses them because the result from sprintf goes back to memory.
Actually, after this compile and link there is a HEX file. Not sure if the code will run or not.

As was pointed out, without the ability to recompile the libraries (with modified zpage and cfg files) you are stuck with the standard zpage layout.
This to me is a major problem for what I had in mind.

It would be nice to get this compiler working and to see some (even if limited) support from WDC. It could only benefit them in the long run.

(Off topic)
I receive a first (prototype) 6502 PCB in a few days. Was to lazy to breadboard or use vero board. Some people have too much time.
Was hoping to have the compiler ready to test. The board is pretty much just CPU + memory + 2 expansion slots. I did breadboard a potential video card based loosely on Ben Eater's videos. Bread boarding it is painfully slow and fixing errors means hours of rework. I bought an Altera CPLD programmer and dev board instead. Much easier to change logic on the fly.

Please keep this post alive with new information on the compiler, bug reports/fixes, etc. anything you think will help others.

I will try to use the compiler and see how far I get.

Thanks
Andre

(Welcome!)

Hi Andre, welcome and thanks for helping try to get the compiler working. I was able to get some simple test code working but I get the same errors as you when I try to use sprintf. I also get the annoying non-sensical error messages. I think if I were ever to use this compiler, I would find some pre-existing tool that checks C code for errors and let that run first.

If you just need a C compiler, have you tried CC65? The output is not especially well optimized (hence our interest in WDC) but it's very reliable and doesn't force you to recompile libraries when you change zp usage or anything stupid like that.

EDIT: and you may want to avoid sprintf and printf anyway since they can take up a huge amount of ROM even when you're only using a small percentage of their functionality. I just handle strings myself since something like puts is basically a 1 line function. You can devise sprintf/printf functionality with very, very little code if you know exactly what you want. I've done something like this in C with CC65: PrintInt("Three is % and five is %", 3, 5); You can give a dummy argument for the second int if you only need to print the first one in the string.