Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

An actual TrollCPU

Name: Anonymous 2016-10-13 17:28

https://en.wikipedia.org/wiki/NCR_315
The instructions could use a memory slab as either two 6-bit alphanumeric characters or as three 4-bit BCD characters
The addressable unit of memory on the NCR 315 series is a "slab", short for "syllable", consisting of 12 data bits and a parity bit
A slab may contain three digits (with at sign, comma, space, ampersand, point, and minus treated as digits) or two alphabetic characters of six bits each.
A slab may contain a decimal value from -99 to +999.
A numeric value contains up to eight slabs. If the value is negative then the minus sign is the leftmost digit of this row.
There are instructions to transform digits to or from alphanumeric characters.

Name: Anonymous 2016-10-13 19:43

Decimal computing and COBOL were mainstream at one time. Addresses were decimal too.

Name: Anonymous 2016-10-13 19:46

I'd take native decimals over imprecise floats in a heartbeat.

Name: Anonymous 2016-10-13 19:54

We should have an arbitrary-size integer type, automatically allocating and freeing memory as appropriate to hold its current value. This could be used to implement an arbitrary-precision floating point type, by having the mantissa and exponent both being arbitrary-sized integers. It should also be possible to store rational expressions directly, rather than approximating them with a float. Otherwise, there is no way to directly represent quantities like 1/3 in either binary or decimal.

Name: Anonymous 2016-10-13 22:26

I'm surprised that was real computer. And people say x86 is bad...

Name: Anonymous 2016-10-13 22:37

Otherwise, there is no way to directly represent quantities like 1/3 in either binary or decimal.

let one_third = "1/3"

Name: Anonymous 2016-10-13 22:57

>>6
Huskell niggers need not apply

Name: Anonymous 2016-10-14 12:25

Lots of retards on the thread do far. You dopes clamoring for decimal hardware should go get an early copy of TAoCP, with the MIX machine instead of the MMIX, and see what a complete pain in the ass it is to try to do anything in a way that will actually take advantage of decimal types while still not horribly breaking in binary modes.

>>7
That's clearly Swift.

Name: Anonymous 2016-10-14 12:46

>>8
No, it's obviously O'Caml.

Name: Anonymous 2016-10-14 13:18

>>8
Not a problem if you use decimal logic[1] instead of binary logic.

[1] Implementation of decimal logic in hardware is left as an exercise to the reader.

Name: Anonymous 2016-10-14 14:03

Binary logic is too oppressive and hetero-normative.

Name: Anonymous 2016-10-14 14:18

http://xyzzy.freeshell.org/trinary/CPE%20Report%20-%20Ternary%20Computing%20Testbed%20-%20RC6a.pdf

Name: Anonymous 2016-10-14 14:24

>>10
Buy an HP calculator, the Saturn processor is BCD based.

Name: Anonymous 2016-10-14 14:46

>>1,12
6bit Chars should be enough for reduced ASCII,and its exactly 2 trits.

Name: Anonymous 2016-10-14 14:55

>>14
False. 6 bits has 64 unique states, 3 trits has 9 unique states.

Name: Anonymous 2016-10-14 15:25

>>14
>>15
Calm down, you're both wrong. A block of 3 trits can have 27 different states (33).
Also, with 6 bit chars, you can snuggly fit 6 of them in one PDP double word and store one C89 external identifier in such a word.

Name: Anonymous 2016-10-14 15:30

>>16
middle-endian ternary would be a joy to program in.

Name: Anonymous 2016-10-14 15:47

>>17
1.Normies and compiler writers BTFO(porting to ternary will require human labor)
2.Programmers salaries increase
3.Ternary provides best(closest to e(2.71)) information density
4.Neat bithacks exploiting middle-endian format
5.Ternary is faster and allow storing more data in memory.
6.AI switches to fuzzy ternary logic(true,unknown,false)
7.Networks which use Middle-endian ternary would be much harder to hack or eavesdrop into

Name: Anonymous 2016-10-14 16:02

>>18 A slight suggestion:
Protocol buffers encoding on top of middle-endian ternary.
https://developers.google.com/protocol-buffers/docs/encoding

Protocol buffers have many advantages over XML for serializing structured data. Protocol buffers:

are simpler
are 3 to 10 times smaller
are 20 to 100 times faster
are less ambiguous
generate data access classes that are easier to use programmatically
https://developers.google.com/protocol-buffers/docs/overview

Name: Anonymous 2016-10-14 16:19

Also Floating Point should use base 2.71(log e)
Its has many mathematical advantages and is optimal for data storage.
https://en.wikipedia.org/wiki/Natural_logarithm

Name: Anonymous 2016-10-14 22:58

>>18-20
Spotted the FrozenAnus.

Name: Anonymous 2016-10-14 23:36

>>22
CHECK MUH DUBZ
Don't change these.
Name: Email:
Entire Thread Thread List
All trademarks and copyrights on this site are owned by their respective parties. All comments and posts are the responsibility of their own posters.
- Tinychan + 2ch Mode + RSS -