the real (pun intended) answer is that all of us wish `real` wasn't a thing so it's implemented in the most "just fuck off already" way possible
-
-
Replying to @whitequark @The6P4C
there's a bunch of other features that are also like that
1 reply 0 retweets 2 likes -
-
Replying to @The6P4C
fun fact i still don't know what *exact* semantics it implements. i just know it does... something... about the bits
2 replies 0 retweets 2 likes -
Replying to @whitequark
i know i'm "upto" my neck in parsers, that's for sure
1 reply 0 retweets 4 likes -
Replying to @The6P4C
i mean i know that wire [3:0] is downto and wire [0:3] is upto, but i have no idea what happens if you e.g. connect the two
1 reply 0 retweets 1 like -
Replying to @whitequark @The6P4C
i suspect what happens is not what you actually want but i don't know what it is
2 replies 0 retweets 1 like -
Replying to @whitequark @The6P4C
it's probably for that insane "least significant bit is 31" numbering scheme
1 reply 0 retweets 4 likes -
Replying to @whitequark @The6P4C
IBM says hi. Because they don't go big endian, they go BIG endian. Yes, bits are also packed from the top first. Unused bits are the LSBs.pic.twitter.com/jATuc7kWy4
4 replies 0 retweets 19 likes -
Half of understanding rlwinm is being able to count upwards, not downwards.
1 reply 0 retweets 6 likes
rlwinm_emu.py ¯\_(ツ)_/¯
-
-
plz stop leaking the contents of my local disk
0 replies 0 retweets 3 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.