Annatar

86 ms·

811.
by Annatar 8y ago
If you look at all the modern muscle cars (or in the case of the Corvette and Camaro ZL1) hypercars and supercars camouflagef as muscle cars, they all come with the manual transmission as the standard option, and most of the enthusiasts cho
812.
by Annatar 8y ago
It's a demo. Coded in assembler. On a horribly slow (4 MHz) Russian PDP-11 clone with no DMA capabilities. 72 cycles to move a word from one memory location to another. http://www.pouet.net/prod.php?post=836903 As such
813.
by Annatar 8y ago
Maybe this will finally stop the horribly misguided "noone programs in assembler any more" comments here on "Hacker News" (especially during yet anothet RISC V marketing campaign).
814.
by Annatar 8y ago
Quite a lot of code is written in assembler, especially if one is in the demo and cracking scene. Low level driver implementations are often written in assembler. Machine implementation details of the kernel are written in assembler. Operat
815.
by Annatar 8y ago
More marketing for a processor with horrible assembler instructions which exists only in a tinkertoy. Because in IT everybody has to re-invent the same thing over and over again. No technology is discussed.
816.
by Annatar 8y ago
But they were available, and most of us used the optical character recognition scanned version on the LSD doc disk. 25 years later I bought the real thing.
817.
by Annatar 8y ago
And yet, this smaller tech comes directly from SGI: lots of former SGI hardware engineers ended up at NVIDIA.
818.
by Annatar 8y ago
Had the server version of this system as my private server in my basement at home; the electricity bill was peppery. I must have torn it apart and put it back together about ten times, studying the hardware, and must have installed IRIX 6.5
819.
by Annatar 8y ago
Yes, please don't do it, for no primitive intel-based system has ever come close to any SGI hardware in terms of elegance. It would be a sacrilege.
820.
by Annatar 8y ago
" Hardware doesn't come with programming manuals anymore as it is deemed too complex (yeah right) and expensive. " It doesn't come with manuals because it is considered a trade secret. Commodore had to lay the hardware b
821.
by Annatar 8y ago
" I think the people that first encountered computers when they were relatively simple and constrained have a huge advantage over the rest of us. Today, (almost) everyone knows how to use a computer, but very few people, even in the co
822.
by Annatar 8y ago
What about OpenSPARC, since it has low power consumption and can be cut down to less cores and threads?
823.
by Annatar 8y ago
That's a jip! We should be changing to Winter time and get the hour we lost back! We're going to get shafted in this deal!
824.
by Annatar 8y ago
You can have a "phenomenal" processor design (Itanium was "phenomenal") in that sense, but if it's crap to program, it's not going to do it much good. As you've so aptly demonstrated, RISC-V is crap to pro
825.
by Annatar 8y ago
"Indeed, in RISC-V, full 32-bit constants must be broken across two instructions." Any RISC processor has that issue, because encoding is fixed at 32-bits to keep the hardware simple. That's not what I'm referring to. Lo
826.
by Annatar 8y ago
Interesting project.
827.
by Annatar 8y ago
Retardation, by definition, is something backward, and RISC-V instruction set is backward, since it is empathically not an improvement over what we already have in OpenSPARC or MC68000 in terms of clean design or intuitiveness. Perhaps you
828.
by Annatar 8y ago
Motorola assembler is what is known as orthogonal instruction set. The flow is logical: move.b for byte, move.w for word, move.l for longword, from source to destination, which reflects real life. The assembler reads almost like a high leve
829.
by Annatar 8y ago
Again: have you looked at the assembler code? Are you able to compare MC68000 assembler and RISC-V assembler? Are you able to compare SPARC assembler and RISC-V assembler? Without being able to do that, it's going to be exceptionally d
830.
by Annatar 8y ago
If wishes were horses, beggars would ride.
831.
by Annatar 8y ago
"The main motivation for the darkriscv is create a migration path for some projects around the 680x0/coldfire family." On the Amiga we don't need a replacement for MC680## processors because we have the Vampire 2+ accele
832.
by Annatar 8y ago
Well we disagree vehemently: writing clean C code that compiles with any ANSI C compiler is pretty damn easy. Take BIND for example, a non-trivial piece of software which compiles with any compiler.
833.
by Annatar 8y ago
I have no idea what you're writing about.
834.
by Annatar 8y ago
The mechanical internals between a consumer grade and an enterprise drive from the same manufacturer are usually identical and might only differ in things like read and write cache sizes. Firmware is the only thing that matters, especially
835.
by Annatar 8y ago
LISP sympathizer here: I don't need yet another theoretical exercise in how to do computation in LISP, I need a concrete example of how to load and use getopts LISP code to construct command line programs in CCL (for example with CLON
836.
by Annatar 8y ago
It doesn't tolerate power loss at all; it doesn't have any kind of facilities to do that, and write barriers will only work if the underlying storage supports it, otherwise ext4 will revert to no write barriers, so it's spott
837.
by Annatar 8y ago
"I wrote "a lot of its capabilities are much more relevant for large servers" Which is true." That is a myth. It's simply not the case. What you could argue is that if you solve a problem for servers, it is also sol
838.
by Annatar 8y ago
The better the drives, the better the performance and data integrity with ZFS, but WD is really consumer grade hardware: Seagate ES or Hitachi enterprise drives have completely different firmware.
839.
by Annatar 8y ago
"This is the first time I've heard this expression." Slide 18, "ZFS loves cheap disks", underlined. https://wiki.illumos.org/download/attachments/1146951/zfs_la... I've been runn
840.
by Annatar 8y ago
Write cache should always be disabled, even if one is running multimillion dollar storage arrays, no ifs, buts, or maybes. That goes without saying, it's the holy law of data integrity to any storage architect who understands the intri

More ›