by default sdcc behaves as if all locals (parameters, too) are `static`. in fact it will overlap the storage of parameters of all leaf functions. you can turn that off and it uses stack as you'd expect
-
-
Replying to @whitequark @11rcombs
Or you can use a PIC where there is no data stack at all and then if you still need reentrancy haha good luck you need to emulate the stack using a pointer somewhere and indirect accesses. But reentrancy would overflow the 8-level callstack anyway. 2-level on some PICs.
2 replies 0 retweets 7 likes -
or possibly relooper the code?
1 reply 0 retweets 0 likes -
at this point you could implement a VM for something sane in PIC assembly and just switch to programming that
2 replies 0 retweets 11 likes -
Like Brainfuck.
1 reply 1 retweet 6 likes -
avr emulator on pic? :trollface:
2 replies 0 retweets 4 likes -
If I decide that I hate myself enough to actually try to do this, what is the most usable PIC devboard in the current decade?
2 replies 0 retweets 1 like -
To be fair, they're talking about 8-bit PIC. The 16-bit families (PIC24/dsPIC3x) are a much saner register based architecture. And PIC32 is just MIPS.
2 replies 0 retweets 0 likes -
Replying to @azonenberg @rqou_ and
The thing is there is zero reason to use a dsPIC or a PIC32 over some random ARM as far as I can tell. And I wouldn't call dsPIC "sane"... I tried using them once...
3 replies 0 retweets 2 likes -
Replying to @marcan42 @azonenberg and
Price. Bottom end PIC is still worth using when you need a CPU that’s <$0.30 in lowish quantities.
1 reply 0 retweets 1 like
If you need a really cheap micro though, you go for chinese stuff. And dsPICs certainly aren't $.30, more like $1.80 all the way up to $10+. At that price point, just use ARM.
-
-
Replying to @marcan42 @azonenberg and
Absolutely. Can’t think of any reason at all to use the dsPIC. For the really cheap chinese stuff, there’s a weird gap where ordering 20 is fine but order 400 and suddenly you end up in lead times from hell. A lot of what I do is exactly in that range.
1 reply 0 retweets 1 like -
Replying to @james_a_craig @marcan42 and
Sorry, realise now that I’m basically just agreeing with your original comment.
My comment was more for the thread as a whole rather than directly in response to your point about dsPIC. You’re right.1 reply 0 retweets 1 like - Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.