Author: elfprince13
Posted: 01 Nov 2012 09:50:32 pm (GMT -5)
We define the calling conventions for code generation, that's why I was asking for your input.
Let's split a new topic now, and try and get this on it's feet. The thing about having a z80 target for LLVM, is that pretty much *anything* can be compiled to it, not just C, because there are many many compilers and languages that use LLVM for compiling. And LLVM is supposed to have very good optimization, so I suspect that unless we really botch the z80 side specifically (register allocation), that we ought to get good performance. There is an option to write a machine code optimizing pass as well, so we could always try that later if we aren't satisfied.
Do you have a preference for source hosting? GitHub? SourceForge?
_________________
StickFigure Graphic Productions || VSHI: Vermont Sustainable Heating Initiative
![]()
![]()
![]()
Posted: 01 Nov 2012 09:50:32 pm (GMT -5)
We define the calling conventions for code generation, that's why I was asking for your input.
Let's split a new topic now, and try and get this on it's feet. The thing about having a z80 target for LLVM, is that pretty much *anything* can be compiled to it, not just C, because there are many many compilers and languages that use LLVM for compiling. And LLVM is supposed to have very good optimization, so I suspect that unless we really botch the z80 side specifically (register allocation), that we ought to get good performance. There is an option to write a machine code optimizing pass as well, so we could always try that later if we aren't satisfied.
Do you have a preference for source hosting? GitHub? SourceForge?
_________________
StickFigure Graphic Productions || VSHI: Vermont Sustainable Heating Initiative
