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

eat shit cudder

Name: Anonymous 2018-07-27 0:50

Name: Anonymous 2018-07-27 4:59

Bad: CISC, RISC
Good: EPIC/VLIW

Name: Anonymous 2018-07-27 5:04

EDGE

Name: Cudder !cXCudderUE 2018-07-28 5:33

Brain-damaged academics with no appreciation of reality, as usual...

Compiled code only used a few CISC instructions anyways[sic]

That's because compilers are, as I've already mentioned here countless times, still absolutely fucking retarded when it comes to good instruction selection. RISC is an equally retarded architecture, trying to make it impossible for a human to beat a compiler because it's so dumbed down that there's no way to generate better code. Instead of making compilers better, they're making everyone else worse to make themselves look better in comparison.

Enable pipelined implementations

That's not a RISC advantage since the P6's uop decoding.

CISC executes fewer instructions per program (~3/4X instructions)

...more like "an arbitrary amount less" for things like REP MOVS/STOS/CMPS.

99% Processors today are RISC
Quality != quantity. Shitty MIPS is everywhere in stuff you don't even know about.

Widely agreed (still) that RISC principles are best for general-purpose ISA

Absolute Bullshit. Maybe only among the RISC circlejerkers.

Security
Scaremongering authoritarian freedom-haters.

What if there were free and open ISAs we could use for everything?
386/486. Pentium patents are expiring soon if they haven't already.

Curious lack of any mention of the horrible instruction density and the memory bandwidth bottleneck in those slides... really makes you wonder how deluded these fucktards are.

I've said it before and I'll say it again: CISC can always get faster by moving microcoded instructions into dedicated hardware. Good luck trying to "decompile" a series of RISC instructions back into an operation that can be performed on dedicated hardware when it becomes available like a multiplier, divider, AES round, etc.

Name: Anonymous 2018-07-28 13:58

Security
Scaremongering authoritarian freedom-haters.

Legacy architectures like x86 are almost certainly riddled with undiscovered side channel attacks like the ones that surfaced recently. You can't hand wave that away.

And in terms of freedom, we have more to worry about from proprietary blobs like IME rather than hardware that adheres to a free and open spec.

Name: Cudder !cXCudderUE 2018-07-28 16:39

side channel attacks

I'm not running a cloud datacenter with thousands of users sharing the same hardware, I don't run untrusted (by me, not some corporate-and-government-deepthroating authority) code, I don't care about by-design "attacks" that aren't part of my security model.

tl;dr: No fucks given.

Name: Anonymous 2018-07-29 1:28

>>4
Good luck trying to "decompile" a series of RISC instructions back into an operation that can be performed on dedicated hardware when it becomes available like a multiplier, divider, AES round, etc.
Good thing, you will have the source available so you will be able to recompile them.

>>5
Fun fact: Itanium was not affected by spectre nor meltdown as it does not use branch prediction.

>>6
Enjoy random assholes stealing your RSA/AES keys because they happened to make an https request to your server.

Name: Anonymous 2018-07-29 2:40

CISC executes fewer instructions per program (~3/4X instructions)
So CISC executes fewer instructions per instruction (kind of)?
Say 90% is done by 10% of instructions, and then the other 10% probably must take 30-40 Risc instructions

Name: Cudder !cXCudderUE 2018-07-29 3:39

Good thing, you will have the source available so you will be able to recompile them.
No one wants to fuck around with that deliberate planned-obolescence bullshit.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List