nesdev.com

Huh? How it can be 17/24? I count 6 falling edges when M2 falls. And M2 changes *only* on falling edges of the master clock... For the duty cycle to be 17/24, M2 would have to change state on a raising and falling edges, wouldn't it? And sadly, I can't decipher die photographs (yet?), so I can't see...

lidnariq wrote: ↑

Wed Sep 30, 2020 3:59 pm

(Also: does anyone have a 2A03letterless and can test what the actual duty cycle of M2 is? It's not 3/4.)

Long ago, I took that measure and yes, it's ¾. Not the best measurements in the world, but it can clearly be seen.

Reproduced the preview thing. I just basically spam-clicked the "Submit" button, and saw my useless post in the preview. That's bad, it looks like the "submit" button just sends the post text and the server software either can't know if it has already processed the post, or just ignore/don't care th...

(testing double submit, ignore this/these post(s))

Sound samples of these would be nice.

It is "third". A C preprocessor just expands until 1) there's nothing left to expand, or 2) while expanding, it encounters a macro that was already expanded before (in the same expansion context), and let it as it is, to prevent any recursion. That means #define foo bar, baz #define bar foo, bar "fo...

the string substitution, just stack alloc the temp buffer, that should easily handle every thing a sane person would through at a 6502 assembler. So make a large buffer, then start from the back and expand as you need to doing find replaces. Keep the src and convert one into the buffer going forwar...

You seem to worry too much about optimizations at this time; even worse, you're worrying about how to manage memory down to the macro-handling code. Your time will be much better spent on how to structure things and separate concerns. Strings, for instance, are best managed in objects with a minimal...

Controllerhead wrote: ↑

Tue Aug 18, 2020 7:39 pm

Two pages ago, someone asked for a CPU with a math-like syntax (or C-style syntax), instead of a "COBOL" like syntax (oops, mixing things up with the other thread). Here it is, my friends: CSR's Kalimba processor . Just look at the assembly code, it really looks like C at times. Not too surprisingly...

That's a bummer. I hope you get better.

You have some fine stuff, but I'm in Canada.

What's up, dude? Your health problems aren't too serious, are they?

I've been having problems with clang builds being crashy. Extra crashy if compiled with -O3, or pgo, but still crashy (and slower than real-time) even at -O0. Mostly in the debugger. A gcc build seems ok. Since this sounds like "compiler bug" I don't even think you're the right person to mention th...

Wait, two C compilers released less than a week apart? What's this, the year of the C compilers? That being said, that's awesome.

I know some members here would like to see some code examples, like what the equivalent of a hand coded memcpy in C looks like in assembly once compiled.

I can't agree more with this. Programming is something you learn by doing it. It really helps when you have some environnement where you can freely experiment and do things that works or that crashes and burns — both are valuable experience. Back in college, I learned assembly (self-taught) on PIC m...