[Vm-dev] unit code for new faster bitblt
Casey Ransberger
casey.obrien.r at gmail.com
Tue Jun 25 23:38:55 UTC 2013
On Jun 25, 2013, at 3:17 PM, tim Rowledge <tim at rowledge.org> wrote:
>>> On 25-06-2013, at 1:02 AM, Stefan Marr <smalltalk at stefan-marr.de> wrote:
>>>>
>>>> How about just decompiling the binary (i.e. the compiled ASM code) to the proper format?
>>>
>>> if you know a way to do that and get readable, maintainable code at the end, do please let us know. That would be a seriously useful trick!
>>>
>>>
>>> tim
>>> --
>>> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
>>> Useful random insult:- If you give him a penny for his thoughts, you get change back.
>>
>> Wait. I thought we were talking about assembly language! :P
>
> Ooh, snap. It *is* just about possible to write clear, maintainable assembler code, just like it is in theory possible to write a clear, intelligible tax code.
>
> tim
> --
> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
> Strange OpCodes: ESC: Emulate Small Child
The main problem in my view with both systems: they predate garbage collection. If the tax codes ever threw anything out, we wouldn't be in this mess:)
Okay, just so I'm not burning all my bandwidth on snark here, is there a repo where I can look at all the code?
I'm more familiar with Intel syntax myself but I do enjoy a spot of assembler once in awhile. AT&T syntax is yucky and kind of scary, but it's just syntax and that's not too bad.
I have a Pi and I've been looking for some way to contribute around that. Maybe I can help with this and learn about the Pi's graphics facilities while I'm at it. That could be fun.
More information about the Vm-dev
mailing list