lefticus's comments

On: Compiler Explorer – now with side-by-side compiler comparison

[lefticus]

Turbo styled theme would be awesome

On: C++14 for the Commodore 64 [video]

[lefticus]

This was another reason I went the x86->6502 route instead of just a 6502 backend for llvm - it could plausibly work with any code. Let me know what you find.

On: C++14 for the Commodore 64 [video]

[lefticus]

Functional calls are not handled, which is part of the problem. There are several working examples in the x86-to-6502 repository. Please add more examples and help with additional translation.

On: C++14 for the Commodore 64 [video]

[lefticus]

I was unable to get any of the existing 3 llvm 6502 backends to produce reasonable code. Which is why I went this route. I meant to mention that in the video...

[hermanhermitage → lefticus]

There's also https://github.com/puppeh/gcc-6502 and https://github.com/puppeh/gcc-6502-bits to get 6502 directly out of gcc.

[lefticus → hermanhermitage]

I don't believe I found those, thank you.

[smcl → lefticus]

By reasonable code do you mean performant, or just plain working?

[Hydraulix989 → smcl]

If I had to guess, now knowing that there's a crushing stack size limitation for 6502 CPU, probably "just plain working."

On: How The Commodore 64 Memory Map Worked [video]

[lefticus]

Here, the are spec'd as unused bits returning 1: http://www.antimon.org/code/vic2.html

[rrauenza → lefticus]

Ah, thank you. It appears it is only a 4 bit memory location and the spec says the unused bits always return 1's.

On: How The Commodore 64 Memory Map Worked [video]

[lefticus]

It did not explain why, I'm assuming it's a property of the VIC, but I haven't looked into it yet.