Hehe, indeed ...

I've been using (RCS,) Clearcase and Subversion. Just for mfakto I'm using git (in order to learn and see how it works). It sure helped me a lot. But lacking the ton of contributors, there's not much that the others wouldn't have done. Compared to Clearcase and Subversion I like it's speed and miss the ability to abbreviate it's commands. OK, I recently found out that command completion using tab works in git bash, even on windows - something I did not expect.

[QUOTE=Bdot;364113]miss the ability to abbreviate it's commands.[/QUOTE]

[url]https://git.wiki.kernel.org/index.php/Aliases[/url] ;)

I [B]knew[/B] there was some way ... cool examples, BTW. Thanks a lot!

Not Working with Windows 8.1
 

I had installed mfakto 0.13 and it was working well with Windows 8

Just recently upgraded to windows 8.1 and mfakto no longer works.

It stops at self test 4. I get a pop up saying display driver stopped responding but has recovered.

Here is what I have in the command prompt window form mfakto:

[CODE]mfakto 0.13-Win (64bit build)


Runtime options
Inifile mfakto.ini
Verbosity 1
SieveOnGPU yes
GPUSievePrimes 82486
GPUSieveSize 64Mi bits
GPUSieveProcessSize 16Ki bits
WorkFile worktodo.txt
ResultsFile results.txt
Checkpoints enabled
CheckpointDelay 300s
Stages enabled
StopAfterFactor class
PrintMode compact
V5UserID none
ComputerID none
TimeStampInResults yes
VectorSize 2
GPUType AUTO
SmallExp no
Compiletime options
MORE_CLASSES enabled
Select device - Get device info - Compiling kernels.

OpenCL device info
name Caicos (Advanced Micro Devices, Inc.)
device (driver) version OpenCL 1.2 AMD-APP (1348.5) (1348.5 (VM))
maximum threads per block 256
maximum threads per grid 16777216
number of multiprocessors 2 (160 compute elements)
clock rate 775MHz

Automatic parameters
threads per grid 2097152
optimizing kernels for VLIW5

running a simple selftest ...
########## testcase 4/17 (#30) ###########[/CODE]

The catalyst control centre show the hardware as:

[CODE]Primary Adapter
Graphics Card Manufacturer Powered by AMD
Graphics Chipset AMD Radeon HD 8470
Device ID 6778
Vendor ID 1002
Subsystem ID 8493
Subsystem Vendor ID 1462
Graphics Bus Capability PCI Express 2.0
Maximum Bus Setting PCI Express 2.0 x16
BIOS Version 013.012.000.041
BIOS Part Number 113-AD5O100-105a
BIOS Date 2013/01/16
Memory Size 1024 MB
Memory Type DDR3
Core Clock in MHz 775 MHz
Memory Clock In MHz 900 MHz
Total Memory Bandwidth in GByte/s 14.4 GByte/s[/CODE]


The software listed in command centre is as follows:

[CODE]Driver Packaging Version 13.251-131 206a-1 66389C-ATI
Catalyst Version 13.12
Provider Advanced Micro Devices, Inc.
2D Driver Version 8.01.01.1360
2D Driver File Path /REGISTRVJMAC HINEJSVSTEM/ControlSeto0l/Controlf
Class/{4d36e968-e32511ce-bfcl-08002be10318}I0000
Direct3D Version 9.14.10.0 1001
OpenGL Version 6.14.10.12618
AMD Catalyst Control Center Version 2013.1206.1603.28764[/CODE]

Try this: [URL]http://mersenneforum.org/showpost.php?p=361160&postcount=933[/URL]

Also, set GCN in mfakto.ini instead of AUTO or VLIW5, it may be faster.

[QUOTE=kracker;365939]Try this: [URL]http://mersenneforum.org/showpost.php?p=361160&postcount=933[/URL]

Also, set GCN in mfakto.ini instead of AUTO or VLIW5, it may be faster.[/QUOTE]

I have tried the above with GPUTYPE set to GCN and it still crashes at selftest #4.

I checked the AMD site and I have the latest drivers.

Mantle drivers -beta- is about to be released. Could it help Mfakto?
[url]http://www.tomshardware.com/news/amd-mantle-drivers-download,25927.html[/url]

[QUOTE=gjmccrac;365919]I had installed mfakto 0.13 and it was working well with Windows 8

Just recently upgraded to windows 8.1 and mfakto no longer works.

...
VectorSize 2

...
name Caicos (Advanced Micro Devices, Inc.)

...
optimizing kernels for VLIW5
[/QUOTE]

For Caicos, VLIW5 is correct, but VectorSize=4 will result in better performance. Plus, there is a chance that the display driver does not abort.

In the example that I used to show the problem to AMD, they found a write beyond array bounds, causing the abort in the example. I was not able to see that kind of source code issue in mfakto, but the result is the same ...

[QUOTE=kracker;365939]Try this: [URL]http://mersenneforum.org/showpost.php?p=361160&postcount=933[/URL]

Also, set GCN in mfakto.ini instead of AUTO or VLIW5, it may be faster.[/QUOTE]

Maybe I should round up my current mfakto development state and release the next version ... though I did not manage to get everything done that I wanted.

But VLIW5 is OK for that GPU. What will resolve the abort for sure, is to go back to CPU sieving (SieveOnGPU=0). So far I've seen the aborts only when GPU sieving.

[QUOTE=firejuggler;366041]Mantle drivers -beta- is about to be released. Could it help Mfakto?
[URL]http://www.tomshardware.com/news/amd-mantle-drivers-download,25927.html[/URL][/QUOTE]

Mantle is of great help for ultra-short kernels, like drawing a few 3D-items, because the scheduling overhead is dramatically reduced. For long-running kernels, like mfakto's, I did not yet find a benefit. However, I still have to see if there's an easier way to inline assembly statements - this could help by offering some instructions that are not exposed in OpenCL.

[QUOTE=Bdot;366256]
Maybe I should round up my current mfakto development state and release the next version ... though I did not manage to get everything done that I wanted.
[/QUOTE]

Wow, there are some 8xxx that are [I]VLIW5[/I]? Rebadge at it's finest. :razz:

[QUOTE=Bdot;366256]
But VLIW5 is OK for that GPU. What will resolve the abort for sure, is to go back to CPU sieving (SieveOnGPU=0). So far I've seen the aborts only when GPU sieving.
[/QUOTE]

Sieving on the CPU worked for the 01.4pre version.

There is a CL compile error for ver 0.13 if I set it to Sieve on CPU.

[QUOTE=gjmccrac;366326]Sieving on the CPU worked for the 01.4pre version.

There is a CL compile error for ver 0.13 if I set it to Sieve on CPU.[/QUOTE]

Hmm. Have you tried a fresh install of the latest drivers? (completely remove, reboot, restart etc) I have had to do that a time or two.