TGB1718 Posted February 15, 2021 Share Posted February 15, 2021 Quick question, I decided to give KickC a try, I appreciate it's still being developed, I copied a program I had written for cc65, nothing too fancy in it, but it uses file handling and fails to find <fcnlt.h> I've got the latest release from GitHub but it doesn't seem to be in the include directory, does KickC not support file handling yet ? Quote Link to comment Share on other sites More sharing options...
ilmenit Posted February 15, 2021 Share Posted February 15, 2021 Looking at the github, KickC does not have fcntl.h (nor other filesystem operations) implemented yet. Quote Link to comment Share on other sites More sharing options...
TGB1718 Posted February 15, 2021 Share Posted February 15, 2021 36 minutes ago, ilmenit said: Looking at the github, KickC does not have fcntl.h (nor other filesystem operations) implemented yet Thought as much, did a 'grep' for fopen of all the header files in case it was there somewhere, but nothing. Quote Link to comment Share on other sites More sharing options...
ilmenit Posted February 15, 2021 Share Posted February 15, 2021 (edited) it's a great opportunity to become a contributor to the project! Btw, @TGB1718, maybe this will be useful Edited February 15, 2021 by ilmenit Quote Link to comment Share on other sites More sharing options...
TGB1718 Posted February 15, 2021 Share Posted February 15, 2021 1 hour ago, ilmenit said: it's a great opportunity to become a contributor to the project! Not promising anything, but looks like something I just might do !!! Quote Link to comment Share on other sites More sharing options...
ilmenit Posted February 15, 2021 Share Posted February 15, 2021 12 minutes ago, TGB1718 said: Not promising anything, but looks like something I just might do !!! Would be really cool! Quote Link to comment Share on other sites More sharing options...
Elkino Posted February 15, 2021 Share Posted February 15, 2021 I working in a port of B2FJ (https://mzattera.github.io/b2fJ/) to Atari 800 XL. I'm currently using CC65, but the generated binaries seems to be sub-optimal, as there are many JSR calls for stack handling in the generated 6502 code. Also, seems that the default CC65 binaries images don't use all available RAM on Atari. Will be great if kickc point their efforts to be a drop-in replace for CC65, supporting the same extensions, command-line and arguments than CC65 but with better code generation, then we can port old projects to this new compiler easily. 1 Quote Link to comment Share on other sites More sharing options...
ivop Posted February 15, 2021 Share Posted February 15, 2021 I see your program display 64K RAM system. Theoretically that's correct, but normally only 48kB is available, because 16kB is overlayed with ROM and hardware registers. If ROM is disabled, you get 14kB of RAM extra, but with a 2kB gap of hardware registers. Quote Link to comment Share on other sites More sharing options...
ilmenit Posted February 16, 2021 Share Posted February 16, 2021 14 hours ago, Elkino said: Will be great if kickc point their efforts to be a drop-in replace for CC65, supporting the same extensions, command-line and arguments than CC65 but with better code generation, then we can port old projects to this new compiler easily. KickC is not aiming to be "CC65 with better code generation", therefore I doubt this will be ever done. 2 Quote Link to comment Share on other sites More sharing options...
baktra Posted February 16, 2021 Share Posted February 16, 2021 It would be possible to create an independent front-end. However, the value of such software would be questionable. Depends on how much cc65 options are mappable to KickC. It would always be imperfect. Better to update your build files for KickC. Quote Link to comment Share on other sites More sharing options...
ivop Posted February 16, 2021 Share Posted February 16, 2021 (edited) IMHO it's a good to choice to not make KickC ABI compatible with CC65, because that would mean you are still stuck to the software stack and the same calling conventions. That does not mean you cannot port or reimplement CC65 libraries for KickC ofcourse Edited February 16, 2021 by ivop 1 Quote Link to comment Share on other sites More sharing options...
JesperGravgaard Posted February 17, 2021 Author Share Posted February 17, 2021 Hi, The author of KickC here. @ivop and @ilmenit are correct that the goal is not to be a drop-in replacement for cc65. What I really want to create is a compiler that allows a programmer who knows C an easy way to get started on any 6502-platform, to be able to create C-programs that runs as fast or faster than naively coded ASM, and finally to be able to seamlessly switch to optimized ASM for any performance-critical parts. The semi-prioritized goals of KickC could be stated as: 1) Generate optimized and readable 6502-family ASM. 2) Support different existing 6502-based hardware platforms. 3) Allow the programmer to utilize the strength of KickAsm. 4) Be standard C compatible. However, it would be great if porting CC65 programs to KickC was pretty easy to do. For instance CC65 and KickC can and should have a bunch of libraries that are compatible. An existing example of this is the <conio.h> library. If anyone wants to contribute an implementation of <fcnlt.h> or any other standard C / cc65 library for Atari 8bit I will gladly merge it into the KickC master and include it in future releases. Feel free to reach out to me with any questions. /Jesper 1 2 Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.