Starting to port Prime95 to native UWP

[Bulldozer]

I've just started a project to port prime95 to native UWP/WinRT and launch it to MS Store. Just downloaded the source code. Would anyone that have UWP developing experience give me some suggestions?
Here are the two ways that I planed:
1:Use the classic Win32 prime95 executable and use XAML to make a UWP shell to sync with it.
2:Use the code to develop a full-native UWP app.
Hope for your suggestions. Thanks!

[M344587487]

I have my doubts as to how popular UWP is. From the looks of it the main potential is to be able to run on Xbox, however:

Originally Posted by https://docs.microsoft.com/en-us/windows/uwp/xbox-apps/frequently-asked-questions

Xbox no longer supports x86 app development or x86 app submissions to the store.

Maybe this just means 32bit, maybe it means non-game related apps are barred from the xbox store. So for an end user to run the code they'd potentially have to download your app manually and sideload the app, probably having to swap to/from dev mode whenever they wanted to go between running the app and playing games. Possibly doable but cumbersome, bit of an unknown.

What use case do you see for a UWP port?

[Bulldozer]

Originally Posted by M344587487

What use case do you see for a UWP port?

For all devices to be able to join the project: Windows 10 S, Windows 10 Mobile, Xbox, Hololens and IoT devices.

[xx005fs]

Originally Posted by M344587487

From the looks of it the main potential is to be able to run on Xbox

I don't think it will be worth it to run on those super low clock bulldozer CPUs on the game consoles even with prime95's great optimization. Instead posting a gpu app such as gpuowl would utilize the resources much better as the GCN gpus on xboxes have a lot of compute potentials and a great deal of memory bandwidth.

[M344587487]

Originally Posted by xx005fs

I don't think it will be worth it to run on those super low clock bulldozer CPUs on the game consoles even with prime95's great optimization. Instead posting a gpu app such as gpuowl would utilize the resources much better as the GCN gpus on xboxes have a lot of compute potentials and a great deal of memory bandwidth.

I was thinking of the next gen releasing within a year, both Xbox and PS5 will be octa-core 7nm Ryzen zen2 with Navi GPUs (rumoured to be 36 CU's at 2GHz for PS5 like an OC'd RX 5700, 56 CU's at 1.7GHz for Xbox, the reality is more likely this CU count but clocked lower). gpuowl would be great but AMD have dropped the ball big time on OpenCL support for desktop Navi cards, hacking support into a locked down device sounds non-trivial at least.

[xilman]

Originally Posted by Bulldozer

For all devices to be able to join the project: Windows 10 S, Windows 10 Mobile, Xbox, Hololens and IoT devices.

My, admittedly incompetent, take is as follows. There are at least two (IMAO) laudable consequences of your proposal;:

1) you learn how to do such a thing;
2) all contributions to the project, regardless of whether the computational effort is anywhere near the bleeding edge, is far better than no contributions at all.

I speak (type, actually) as someone who ran factoring code on PPro and a DECstation for something like 5 years after it became economically attractive.

[Bulldozer]

Sorry, but in UWP, assembly is not supported, so I gave up the work of porting prime95 to UWP.
Sorry for Xbox users.

[ixfd64]

I thought x86 assembly was supported?

https://stackoverflow.com/questions/...e-in-a-uwp-app

[Happy5214]

AFAICT UWP is supposed to run on non-x86 platforms (e.g. Windows Phone) without modification, thus precluding direct use of assembly.

[Bulldozer]

[M][/M]After flipping through the development guides of UWP, I found a way that a UWP app can launch an Win32 component without recompiling it. So I'm restarting the UWP prime95 development, and it's estimated to got it's way to the store in 10 days.