>2017 >still using x86 I hope you don't do this, /g/.

>>62201131
I want a nice RISC-V processor, but a decent one probably won't be out for another decade.

I wish, gib actually gud non-x86 CPU that compiles Chromium in <=5 hours

>>62201187
>Chromium
good one mate

>>62201131
it's probably the best architecture and ecosystem that currently exists
I'm going to try RISC-V when it comes out, though

>>62201131

Well, yeah, most modern computers are running AMD64.

>>62201223
My life primarily consists of posting on /g/ and constantly compiling Chromium

>>62201187
Stop being a poorfag and switch to Power.

>>62201131
asuka a shit

>>62201304
Point me to a decent POWER laptop and I will legitimately check it out.

>>62201368
You'll have to wait until portable cold fusion reactors are invented for a POWER laptop to exist.

>>62201368
What are you doing compiling on a laptop in the first place? Just ssh into your server or workstation.

>>62201131
For now I am. My next computer's going to have a MIPS CPU

>>62201368
There's a PowerPC laptop in the works

>>62201484
Some of us do more than just compile gentoo.

>>62201656
And?

>>62201131
86 is bigger than 64, hence it's better.

>>62201131
Who is this seamon daemon?

File: Is-Twitter-Launching-New-Emojis.png (99KB, 2000x2000px) Image search: [Google]

99KB, 2000x2000px

>>62201366
Asuka a LOVE.

WHAT ABOUT CELL PROCESSOR OR LOW-RISK OPEN SOURCE RISK

WHAT IS BEST ARCHETICURE FOR MULTI THREADING CONCURRENCY? AND DEFEATING CIA NIGGErS?

>>62201581
More info, please

>>62201131
I use x86-64 :3

>>62201931
>Cell Processor

Not the best processor for gaming.

>>62201693
And... what? I asked to point out a POWER laptop. You told me to ssh into a server to compile stuff. I'm pointing out how dumb that point is.

>>62201977
https://www.powerpc-notebook.org

>>62201993
You said that you wanted something that was good for compiling. I pointed out that you shouldn't be doing any heavy compiling on a laptop anyway.

>>62201131
currently I'd moved to x86 android emulator cause I have some crashes in camera app with x86_64

>>62201739
Her current state is Russian.

>>62201905
Asuka blyat.

File: 1449995345896.jpg (531KB, 1800x1200px) Image search: [Google]

531KB, 1800x1200px

>>62201986
If it's good enough for the DoD, then it's good enough for me.

File: order.png (61KB, 690x582px) Image search: [Google]

61KB, 690x582px

oh hai

>>62203587
You lucky bastard

>>62201986
Isn't that the processor PS3 uses?

>>62203796
Yes

>>62203796
Yes. It was also criticized by game programmers for being extremely difficult to program for,

>>62201739
https://www.instagram.com/acidjazzsinger/

>>62203887
that's because game dev's are a bunch of lazy fucks that want frameworks to do the work for them automatically.

>>62203887
>>62203987
It's architecture was/is so different than processors found in the Xbox 360 and PCs.

If you were coding a game for the 360 you had to insure that your program was divvying up work between the three general purpose cores effectively. You don't want one core working really hard while the others are sitting their doing nothing. That's not very hard for developers to do since they are more familiar with architecture like that.

Now, for the Cell you have 1 general purpose core and 8 specific cores, and those specific cores are slower. Theoretically, you can get more done with the Cell because you have 8 cores to divvy up the work to. The downside is that when you write code for two or three faster processors it's really hard to rework that code to efficiently use all 8 cores.

Analogy time:

You're a farmer and you have to harvest apples at an orchard. There's 3 rows of apple trees at this orchard and you want to harvest them all in the least amount of time. Since you hired the 360 to do this, you know you have three workers to harvest with and they have baskets big enough to to have each person harvest an entire row without needing to stop. So you write down your plan: "3 people with big baskets, each person harvests a row."

Next Fall we have the same three rows, but we're using the PS3 to harvest apples this time. You have 1 guy with a big basket and 8 guys with smaller baskets. You look down at your plan and realize it won't work. You'd have workers standing around doing nothing and workers needing to empty their baskets because they're full before picking an entire row.

Now you need to take the time to figure out how to coordinate these workers to efficiently harvest your orchard. It will end up possibly being faster if you plan it right, but you had to take the time to plan it, and getting it right isn't a sure thing. That's what's difficult about coding for the Cell.

>>62202048
No I didn't. I didn't mention compiling at all until you brought it up.

File: 14031690_1791100697827068_70276492_n.jpg (25KB, 640x360px) Image search: [Google]

25KB, 640x360px

>>62201131
Asuka needs to get off the krokodil

>>62201131
x86 is mostly fine, it's x64 which has all the back doors

>>62204188
wtf is x64?
Do you mean x86-64? x64 isn't a thing.

File: Screen Shot 2017-09-01 at 3.30.03 PM.png (74KB, 695x244px) Image search: [Google]

74KB, 695x244px

>>62204219
Even Intel refers to x86_64 as x64

File: x86-64.png (7KB, 903x714px) Image search: [Google]

7KB, 903x714px

>>62204219
I think you mean amd64 or x86_64

>>62204023
Acktually, Cell has only one *real* core aka PPE.
SPEs are shitty in-order vector chewing units with very short pipeline, much similar (now you'll understand why it was bad) to the ones employed by Larrabee.
And you know what happened to Larrabee.

>>62204674
>And you know what happened to Larrabee
It became a coprocessor, basically what the SPEs are.

>>62204704
Exactly.
And PS3 had other problems, like shitty nvidia's off-shelf 7 series GPU while 360 enjoyed custom GPU made by ATi (Xenos, the first GPU with unified shaders).

>>62204219
don't be an unnecessarily obtuse fag

>>62204716
One other thing the the 360s favor was shared RAM between CPU and GPU gives you more freedom also had like 10MB of some stupidly fast edRAM that was often used for stuff like HDR