Live data from Hacker News

Apple’s M1 processor and the full 128-bit integer product

lemire.me

81–90 of 180 posts

Re: Apple’s M1 processor and the full 128-bit integer product

#81

A common misconception about RISC processors.

It’s not a RISC thing - CISC implementations do exactly the same kind of fusion for similar pairs of operations.

It has a bit less gain on a RISC due to the code density (or lack thereof), since it requires more fetch bandwidth. Apple works around this by using a very wide front-end: https://news.ycombinator.com/item?id=25257932

Re: Apple’s M1 processor and the full 128-bit integer product

#82

Earlier quoted context omitted.

Not in the next 10 years. Why would they? Fabs are extremely capital-intensive and take years to get up and running, when (like Taiwan Semi) knows how to do it. Intel has shown how hard it can be to do this right. Let TSM work on production (and hopefully get more/larger fabs in the USA up and running) and getting better at packing in the transistors, and let Apple improve the design (and software).

> Why would they? Because Apple has a lot of capital and they wouldn’t need to compete as hard for their share of tsmc production capacity.

I wouldn't considered Apple to be even competing.

They are by far the biggest customer and have a multi-faceted relationship e.g. OLEDs, Modems.

Re: Apple’s M1 processor and the full 128-bit integer product

#83

Earlier quoted context omitted.

Not in the next 10 years. Why would they? Fabs are extremely capital-intensive and take years to get up and running, when (like Taiwan Semi) knows how to do it. Intel has shown how hard it can be to do this right. Let TSM work on production (and hopefully get more/larger fabs in the USA up and running) and getting better at packing in the transistors, and let Apple improve the design (and software).

Why would they make their own M and A processors? They could continue to buy Intel chips and revert back to using PortalPlayer and Samsung chips. Chip designing is capital intensive and takes years to get up and running, when Intel and Samsung know how to do it.

Apple designs their own CPUs, GPUs, SOCs, Modems etc.

And they dominate the competition in performance/power.

Re: Apple’s M1 processor and the full 128-bit integer product

#85
post #51

Earlier quoted context omitted.

> and before anyone asks, yes, I tried a different HDMI cable Have you tried a USB-C/thunderbolt cable/controller tho?

I'm kinda limited in my options, because this MBP only has two USB ports. So I have one port which goes to a USB hub, and the other port goes to an Apple A/V adapter with USB-C power delivery pass-thru, HDMI, and a USB port. If not for my need to have one USB port be switchable, and the rest not, I'd use a USB-C -> DP cable like I use on my 16" MBP. This may prompt me to upgrade prematurely, if/when the next M1 MBP c…

Get a thunderbolt dock and you don’t have to worry about it. The dock also charges my MBA.

Re: Apple’s M1 processor and the full 128-bit integer product

#86

I love my M1, but does anyone else have horrific performance when resuming from wake? It’s like it swaps everything to disk and takes a full minute to come back to life.

Nope, my M1 Air is connected to an external monitor most of the day and I don’t have issues.

Re: Apple’s M1 processor and the full 128-bit integer product

#87
post #78

Earlier quoted context omitted.

They’ve vertically integrated everything else, and they’ve had great success along the way. TSMC has other customers that compete with Apple for production capacity. And there’s geopolitical risk in the region where TSMC (currently) operates.

> They’ve vertically integrated everything else, and they’ve had great success along the way. Why would they want to get into the low-margin, high-risk part of their supply chain, the bit where you can sink billions of dollars and have the value wiped out by a poor choice?

Especially when semiconductor manufacturing has become a major geopolitical flashpoint between China, EU, US etc.

Apple would be insane to get into the middle of it.

Re: Apple’s M1 processor and the full 128-bit integer product

#88
post #16

Anyone want to take a guess at how long it will be until Apple has their own fab in the US making M1 chips?

In the past, haven’t they made exclusive deals with manufacturers by helping them spin up new factories in exchange for exclusive access for X number of years?

IIRC, Apple basically made "retina displays" happen - when nobody else would make that expensive step - by telling a screen manufacturer "here is a very large check; build a factory to make these at commodity scale, within one year."

Re: Apple’s M1 processor and the full 128-bit integer product

#89
post #40

Did anyone actually look at the machine code generated here? 0.30ns per value? That is basically 1 cycle. Of course, there is no way that a processor can compute so many dependent instructions in one cycle, simply because they generate so many dependent micro-ops, and every micro-op is at least one cycle to go through an execution unit. So this must mean that either the compiler is unrolling the (benchmarking) loop,…

The conclusion seems based on the relative execution times for the two benchmarks. Since the benchmarks are measured in the same way, their error bars should be basically the same as well. This analysis is not an analysis of the absolute execution time of these algorithms, but the difference between them.

I don't think the conclusion is hasty. Lemire is saying: "look, if the M1 full multiplication was slow, we'd expect wyrng to be worse than splitmix, but it isn't".

Re: Apple’s M1 processor and the full 128-bit integer product

#90

Earlier quoted context omitted.

This happens to me too, I’m using 1Password. I have a suspicion the plug-in is involved with this but I’ve not had time to collect evidence yet. Seems to be rare though, I’ve not spotted anybody else with this issue.

I am seeing lots of spinning balls with 1Password on my 2015 Macbook Pro. Even just switching between fields with the keyboard brings up a spinner for two seconds or so. It's a recent thing I think. No other app has any issues.

Is it possibly due to the x86 emulation? I could see something like that being the cause
Post reply on HN