llvm-6502 icon indicating copy to clipboard operation
llvm-6502 copied to clipboard

Plans for upstream inclusion?

Open dafyddcrosby opened this issue 10 years ago • 3 comments

Are there plans for this to be submitted in the upstream LLVM? Or is this just a proof-of-concept?

dafyddcrosby avatar Sep 10 '15 17:09 dafyddcrosby

I am viewing this in 2016.

What work still needs to be done to get this ready for upstream?

It appears that this fork has about a year's worth of merging to do from llvm upstream.

chuckhacker avatar Jul 12 '16 19:07 chuckhacker

Hi. This was indeed just a proof-of-concept, and as a matter of fact, I could never get it to work. Unfortunately because of different reasons (mainly lack of time and motivation) I stopped working on it. I should update the README file about the status of this project, if not delete it as it doesn't (and probably will never) work.

munshkr avatar Jul 12 '16 19:07 munshkr

@TheChuckster I was just reviewing the output of this fork it it does indeed seem very far from working - there is no register allocation being done. The closest branch I ever found was this one: https://github.com/beholdnec/llvm-m6502 which generates mostly reasonable code, but you will note here: https://github.com/beholdnec/llvm-m6502/blob/m6502-on-release_38/lib/Target/M6502/M6502TargetMachine.cpp#L23-L31

If you actually try to tell LLVM that you have 8 bit registers and 16 bit addressing you get a crash in llvm at runtime.

the beholdnec fork mostly kind of works if you ignore the fact that it truncates all addresses to 8bit.

If you have any interest in trying to pursue any of these forks, let me know, I might want to help, but I think you'll have to involve the clang team to get answers to these things.

lefticus avatar Jul 18 '16 14:07 lefticus