hi, all. time ago i've found this http://msx.atlantes.org/index_en.html#sdccmsxdos
and successfully setup a SDCC env for msxdos.
Later my hd died.
Now, i'm trying to do the same thing but links on the site are broken.
Someone can point me where to find the files mentioned in the above site ?
Already tryed. And found a lot of problems.
A lot of vdp functions not optimized
Something not OK in the setup.
For example simply declaring a new unsigned int var make a very stupid program to behave differently
Calling fill ram for example cause crash on exit even if the function operate as expected.
Replacing fillvram with my implementation with inline assembler works ok
And other problems like this one.
So I returned to my sdcc library of years ago but I m missing the msx specific files.
It was the original idea. Starting from my lib and adapting to fusion c.
For example I m testing a pset lib for sc2 that I think it 8sbfaster than the already existing.
Planning a circle, line, circle filled etc. But actually maybe I do not recall correctly but I ve noticed that sdcc does an unusual thing when passing parameters to naked function so I still need to setup my old work to verify and adapt the code.
Considering all your posts in every other thread on this site, your requirements for MSX apps exceed anything that is not handwritten assembly. This is a good thing.
Everything you do with SDCC will be a waste of time. Just start writing assembly today, or just in machine code.
I really think you are better off to just start writing assembly directly.
Previous experience showed me that sdcc is not bad if you expect and use it for what it can do.
Anyway the problem is not sdcc vs assembly. It only how to find the files that were in the site I ve mentioned above
But actually maybe I do not recall correctly but I ve noticed that sdcc does an unusual thing when passing parameters to naked function
I don't think so. Parameters are passed on the stack like every other compiler. What is perhaps unusual in SDCC is that it uses ix register to access those parameters. I'm not sure if that's a good thing. But when you write your own assembly, you don't have to use ix, you can use pop and push etc.
Then, if your function takes only one parameter, you can use __z88dk_fastcall, so the parameter is passed in hl register directly.
