[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology

Name
Options
Comment
Verification
4chan Pass users can bypass this verification. [Learn More] [Login]
File
  • Please read the Rules and FAQ before posting.
  • You may highlight syntax and preserve whitespace by using [code] tags.

08/21/20New boards added: /vrpg/, /vmg/, /vst/ and /vm/
05/04/17New trial board added: /bant/ - International/Random
10/04/16New board for 4chan Pass users: /vip/ - Very Important Posts
[Hide] [Show All]


[Advertise on 4chan]


File: bell-curve.png (140 KB, 675x499)
140 KB PNG
ITT we post opinions that instantly out you as a midwit.
I'll start.
>x86 CPUs are actually RISC CPUs pretending to be x86, but Intel won't let you program the real instruction set.
>>
>>109682449
but that's a thing my uni prof told us, well it's not the whole story since there are many more steps (since instructions get reordered, piplined, predicted, ...) in between but it kinda boils down to that
>>
File: Untitled.png (204 KB, 675x499)
204 KB PNG
>>109682449
>>
>>109682478
No, it really doesn't. If anything it's a lot more like VLIW than RISC internally.
>>
>>109682533
i thought intel used some superscalar architecture
>>
>>109682553
What does that have to do with instruction coding?
>>
File: file.png (72 KB, 835x591)
72 KB PNG
>>109682478
It really doesn't. You can see for yourself at uops.info, many of the "complicated" instruction like x86 read-modify-writes are handled by the processor as a single uop implemented directly in hardware. There are no "secret RISC" instructions being used instead.
>well it's not the whole story since there are many more steps (since instructions get reordered, piplined, predicted, ...)
High performance RISC CPUs also do these things.
>>
>>109682602
i had all the hardware shit for only 2 semesters, you really i think i actually know shit?
>>
"Heat death is real"
>>
>>109682449
>goto is the root of all evil
>>
>>109682449
>C is not a low-level language.
>>
>>109682648
That's why it's a midwit opinion. It's held by people who don't know what they're talking about.
>>
>>109682673
but i like being retarded
>>
File: Superior Opinion.gif (82 KB, 1013x661)
82 KB GIF
>>
>>109682701
That's fine. No one person can know everything anyway, but you shouldn't be opinionated about things you haven't learned yet.
>>109682707
Unironically this.
>>
discrot as an excuse for digital only anything
>>
>>109682504
I don't know if anyone believes in that anymore except Jewish grandmas. People just say they do for political reasons.
>>
>>109682449

i have an uncle who moved to a homestead in rural montana to avoid "commiefornia". he homeschools his kids to avoid leftist propaganda and doesn't trust the government.

he also loves his virtual home assistant, his smartphone (which he speaks to via microphone), tesla cars, anything that's big tech and super bad with OPSEC. it's just hard to believe, there's a nonzero chance that the glowies are watching him in particular (especially as someone on the registry).

meanwhile, truly retarded rednecks and high IQ schizos naturally distrust anything with an internet connection or microphone.
>>
>>109682648
That's fine, and the "x86 is just a front for an internal RISC machine" is just a (shitty) teaching analogy to help you understand that instruction decoding is egregiously complicated. However it's nothing like RISC and never was. RISC was an attempt at removing instruction decoding from the CPU altogether by directly encoding the control signals in a fixed machine word that you fetch directly from memory. The goal was simplicity above all else, which leads to incredibly inefficient instruction encoding. This would be completely infeasible to represent internally in a CPU where every bit you add directly fucks you. What they do internally is variable length, terse as hell, and unit dependent. In effect, a better comparison would be VLIW, because that's essentially how VLIW machines function, but that makes for an even shittier metaphor since nobody knows how VLIW machines work.
>>
the meme got the normie hug of death. Best thing you'll get is midwit opinions portraying themselves as high IQ
>>
File: IMG_1866.jpg (129 KB, 1200x885)
129 KB JPG
>>109682449
>>
>>
>>109682449
>Midwit beliefs
>You have to pay for digital consoomer shit
>>
>>109682835
Segfaults are incredibly easy to debug though. GDB will show you the exact instruction that caused the crash and the full callstack leading up to it.
>>
>>109682901
I like languages where print statements are good enough for debugging. I don't want the C cripple crutch.
>>
File: 142351234.jpg (34 KB, 675x499)
34 KB JPG
>>
>>109682449
>>109682478
For the last 30 years both RISC and CISC split instructions into microoperations, the only real remaining difference is that RISC operations can only read or only write, while CISC can perform read and write in one operation. Even that is probably no longer true.
>>
>>109682504
2pbp
>>
>We have achieved AGI
>>
File: 1732501101037368.jpg (86 KB, 844x1024)
86 KB JPG
>>109682707
except im not implying
>me on the right
>>
>>109683009
>Even that is probably no longer true.
Nope. AArch64 has a suite read-modify-write instructions now since version 8.1.
>>
File: IMG_2564.jpg (59 KB, 371x570)
59 KB JPG
>>109682999
ACKK-
>>
>>109682449
but this is essentialy true, the x86 CISC instructions are translated into RISC bytecode. There's no "hidden" instruction set though.
>>
File: IMG_1870.jpg (129 KB, 1200x885)
129 KB JPG
>>
>>109683449
>the x86 CISC instructions are translated into RISC bytecode
Prove it or admit you're a midwit saying things you don't actually know.
>>109682639
>>
python is OK
C++ is OK
AI is le bad
>>
>>109683476
these are my actual opinions btw, I'm a self-loving midwit
>>
>>109682449
>x86 CPUs are actually RISC CPUs pretending to be x86, but Intel won't let you program the real instruction set.
every time someone says dumb shit like this I point out that it's a proprietary implementation and ISA and impossible to prove. that usually ends the conversation immediately
>>
>>109683479
That's based, gotta admit it.
>>
>>109683009
The ISA itself is the abstraction and it doesn't matter what happens behind that on the hardware side, CISC is always CISC and RISC is always RISC. There is no "emulating it" on the hardware side, micro-operations play no role in the abstraction of the op set to high-level languages outside of performance reasons

If i can't switch the target triple to use aarch64 and load it on a CISC processor it isn't RISC.
>>
>>109683449
there's zero way to prove this so it isn't real
>>
>>109682449
Unused ram is wasted ram
>>
>>109683573
That's a good one. People who should know better say that WAY too often.
Related,
>premature optimization is the root of all evil
>>
>>109683545
>>109683470
https://fanael.github.io/is-x86-risc-internally.html
>>
>>109683621
Good post. It needs a Zen update though, because both it and Atom fuse
add [edx], eax

into 1 uop instead of 2 like Sandy Bridge.
>>
>>109683677
Actually never mind, the last paragraph covers that.
>>
>>109682802
Boomers man. Not only do they believe in it but many would disown their own children if it were questioned.
>>
>>109683807
>>109682802
you live in an echo chamber
>>
File: problem.jpg (61 KB, 500x555)
61 KB JPG
>>109683573
>t. firetroon dev
>>
>>109682664
When they made C they called it a high level language because they compared it to assemblers
>>
>>109684271
Did they actually? I've never heard this and can't find anything about it by googling.
The preface to K&R says the opposite.
>C is not a "very high level" language, nor a "big" one, and is not specialized to any area of application.
>>
File: IMG_1880.jpg (157 KB, 1200x885)
157 KB JPG
>>
File: 1788067632616.png (25 KB, 1080x269)
25 KB PNG
one day it will arrive and work



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.