Exploring .NET Core platform intrinsics: Part 4 – Alignment and pipelining

Re:Exploring .NET Core platform intrinsics: Part 4 – Alignme... by rossnordby on Saturday July 21, 2018 @09:52PM (#17584855)

Seeing the intrinsics APIs get filled out- in the open, no less- has been pretty exciting. The fact that something like AES would be implemented competitively in C# is not something I would have predicted even five years ago.

It's remarkable how fast the language and runtime have evolved for performance. It wasn't that long ago that I was manually inlining Vector3 operators to try to get a few extra cycles out of XNA on the Xbox360.

[ Parent | on HN ]

Re:Exploring .NET Core platform intrinsics: Part 4 – Alignme... by pjmlp on Monday July 23, 2018 @02:16AM (#17590881)

The Xbox360 runtime was notorious bad and suffered from the WinDev/DevTools difference of opinions how the future of WIndows development should look like.

Hence killing XNA when they took over Windows 8 development, WinRT and such.

It took all the reorganizations and change of politics, for the .NET Runtime finally start getting some additional love regarding performance.

[ Parent | on HN ]

Re:Exploring .NET Core platform intrinsics: Part 4 – Alignme... by oceanswave on Monday July 23, 2018 @08:49AM (#17592338)

> The Xbox360 runtime was notorious bad and suffered from the WinDev/DevTools difference of opinions how the future of WIndows development should look like.

The past tense structure makes it sound like progress has been made on this front while it’s still the same problem presently. It’s just that those tools in particular have been deprecated (and not replaced)

[ Parent | on HN ]

Re:Exploring .NET Core platform intrinsics: Part 4 – Alignme... by pjmlp on Monday July 23, 2018 @09:21AM (#17592518)

Well, how would you correctly phrase it in proper English then?

That was the reason why the XBox 360 runtime was bad, the remaining of my comment refers to the standard .NET Framework.

[ Parent | on HN ]