Reporting statistics

[[Unknown]]

Some statistics in case anyone is interested. These are statistics of errors, so they more reflect what has problems than what is popular, but it's sorta in between both.

I couldn't be bothered to convert it to bbc, so find it here:
https://github.com/unknownbrackets/ppssp...Statistics

-[Unknown]

[solarmystic]

That was an interesting read, thanks [Unknown].

The reports skew rather heavily towards the android devices, although PCs are getting a good representation up there too. Quite a healthy mix, some of the reported CPUs are cracking me up lol.

[vnctdj]

Interesting

[VIRGIN KLM]

It has quite some intresting stuff there!
* 99 reports from a 16-core setup with 3 issues! LOL

*Intresting to see that on the Intel reports the second most popular reports are from setups that support ALL instruction sets, which proves that atleast half of the people here use a pretty efficient setup that could get benefited from instruction set implementations!

*Something simmilar as above goes to ARM (Even though it's like 1/3rd of the users here), that's really cool!

[[Unknown]]

I can also do statistics on particular OpenGL extensions if anyone has a list of specifically interesting ones. Doing a full list by what's there is hard, unfortunately.

But yeah, cool data.

-[Unknown]

[VIRGIN KLM]

Well, shouldn't OpenGL 4.x have different results to previous implementations? They said they pretty like re-invent OpenGL with those releases (4.x and after).

[[Unknown]]

Well, I don't know, I see things like:

3.1.11931 Compatibility Profile Context (ATI Technologies Inc. AMD Radeon HD 5500 Series), 4.20

I'm not sure what that means, but I assume it means not 4.x. I don't think we're asking for 4.x? There's one card reporting 4.x:

4.2.12217 Compatibility Profile Context 12.10.17 (ATI Technologies Inc. AMD Radeon HD 6700 Series ), 4.20

The latter 4.20 *should* be GLSL version.

-[Unknown]

[xsacha]

I don't think reports are working on Blackberry. Will try and track down why.
You said duplicates are hit for matching gpu/cpu/version but I change version and it's never recorded.

[[Unknown]]

It only checks duplicates based on message. The associated versions, gpus, and cpus for that message are all updated, but the message is not bubbled to the top.

It shows the highest version number for the log entry by the value of the version (example: 760879 for v0.7.6-879-gc9e931e.) If two have the same version, which is shown is indeterminate.

Per the stats, there have been 26 reports from Blackberry devices.

-[Unknown]

[xsacha]

So that is reports altogether or reports that haven't been updated to newer cpu/gpu/version?

I think I've generated more than 26 reports myself which is why I think something is up :\
I even purposely hit some unknown syscalls and didn't see it appear in temp/recent.

I might have a look over the net code later. It should just be regular unix stuff though.

Could I see the most recent report from a Blackberry device?

[[Unknown]]

I'm counting platform hits, so that's all. There's a counter per message for each gpu, each cpu, each platform, and each version. The main intention is to be able to see quickly if the issue is only affecting certain gpu(s) or if it's affecting everyone.

Here are the unique reports from Blackberry devices (26 is just a number):

Code:

| id_game        | formatted_message                                                                    | hits |
+----------------+--------------------------------------------------------------------------------------+------+
| ULUS10457_1.00 | Wrong magic number 46535000                                                          |    4 |
| ULUS10045_1.01 | BREAK instruction hit                                                                |    1 |
| ULUS10457_1.00 | Unimplemented HLE function sceHprmRegisterCallback                                   |   18 |
| ULUS10236_1.00 | sceKernelCreateSema(SNDMUTEX) unsupported options parameter, size = 167769136        |    2 |
| ULUS10537_1.00 | Thread ended within an extended stack                                                |    1 |
| ULES00645_1.01 | sceIoIoctl(disc0:/sce_lbn0x65370_size0x10d73a, 01010005, 09f9fa90, 10, 00000000, 0)  |    1 |
| ULES00645_1.01 | sceKernelStartModule(): doing nothing for some reason?                               |    1 |
| ULES00645_1.01 | sceIoIoctl(disc0:/sce_lbn0x1c640_size0x11d5800, 01010005, 09f9fa90, 10, 00000000, 0) |    1 |
| ULES00645_1.01 | sceIoIoctl(disc0:/sce_lbn0xb6a0_size0x107a000, 01010005, 09f9fa90, 10, 00000000, 0)  |    2 |

-[Unknown]

[xsacha]

Thanks. Looks like it worked then. It's just I am the only one putting in reports, lol.