Dolphin, the GameCube and Wii emulator - Forums

Of lectrode's builds, or the DSP dumper? There shouldn't be much difference between versions with the builds, and the DSP dumper hasn't changed.

(04-30-2012, 10:03 AM)ExtremeDude2 Wrote: [ -> ]

(04-30-2012, 09:08 AM)AndehX Wrote: [ -> ]not sure whats different in the 601 build, but F-Zero GX runs 100% constantly. Only time it ever drops below 100% is during the countdown, but it never goes below 90%

Definately the best build yet.

Compared to?

Every other version i've ever tried lol

translator and fire will have to learn English even give up but maybe toss a dolphin to the Caribe Correct the bug

...
Alrighty...I hope they got that problem solved lol.

(04-30-2012, 09:08 AM)AndehX Wrote: [ -> ]not sure whats different in the 601 build, but F-Zero GX runs 100% constantly. Only time it ever drops below 100% is during the countdown, but it never goes below 90%
Definately the best build yet.

Thx. Glad you enjoy it


-----New Builds-----
3.0-619-g1974938
3.0-629-g77f4786
3.0-630-g1587cb3



These will probably be the last ones I upload before the end of next week
(2012/05/12). If I do upload more during the next week, do me a favor
and tell me to get off here and do my homework

I'm tellin ya...I would soooooo much rather be doing this than calculus...
...and leadership
...and graphic web design
...and most of my other courses


Also, something broke the direct-to-revision links. I will look into this once I
get a chance. I have a hunch that it has to do with permissions or capitalization
vs lowercase characters, as this new host has those things different from my
old host.

I can't find 3.0-630?

(05-07-2012, 06:34 AM)ExtremeDude2 Wrote: [ -> ]I can't find 3.0-630?

Should work now. I forgot to update main host.
Refresh and/or clear browser cache


Edit:
3.0-631-gec0ddb4 is up and ready for Download!

Edit2:
-----Updated all Dolphin revisions list-----

Revision list now also has the SVN revision numbers!

Also, changed the columns:
git describe , SHA-1 , TIMESTAMP , svn revision number (if applicable)

So what happens if i don't have a CPU that supports AVX? Or 4.2? Do i have to use the normal version? Will it just not work or use the existing instructions and ignore optimizations for those not supported? Does it run slower than normal instead?

(05-10-2012, 11:04 PM)Krude Wrote: [ -> ]So what happens if i don't have a CPU that supports AVX? Or 4.2? Do i have to use the normal version? Will it just not work or use the existing instructions and ignore optimizations for those not supported? Does it run slower than normal instead?

It will work normally i think. I have a AMD CPU and am using Lectrode's ICC builds. They are very well optimized and can provide you some speedup (small compared to Intel CPU's).

(05-11-2012, 07:07 AM)hbk Wrote: [ -> ]

(05-10-2012, 11:04 PM)Krude Wrote: [ -> ]So what happens if i don't have a CPU that supports AVX? Or 4.2? Do i have to use the normal version? Will it just not work or use the existing instructions and ignore optimizations for those not supported? Does it run slower than normal instead?

It will work normally i think. I have a AMD CPU and am using Lectrode's ICC builds. They are very well optimized and can provide you some speedup (small compared to Intel CPU's).

It won't work if those "special optimized builds" contain any instructions which aren't supported by the CPU. In that case, the program will just crash with an error message IIRC. If you don't get any error even though your CPU doesn't support that instruction set, that basically means the compiler didn't do any special optimizations for AVX and, in turn, that advertising AVX optimizations is kinda stupid.

(05-10-2012, 11:04 PM)Krude Wrote: [ -> ]So what happens if i don't have a CPU that supports AVX? Or 4.2? Do i have to use the normal version? Will it just not work or use the existing instructions and ignore optimizations for those not supported? Does it run slower than normal instead?

As long as you are using a L101 or higher build, it should not crash
due to unsupported instruction set. My older builds did, but those were
from back long before the switch to GIT.

It uses whatever instructions the CPU currently supports, as long as
they are one of the following: SSE3, SSSE3, SSE4.1, SSE4.2, or AVX.

For example, if the CPU supports SSSE3, but not the higher ones, it
will only use SSSE3. Each set includes support for the instructions of
the previous set, so by saying it uses SSSE3, it will also use SSE,
SSE2, and SSE3 instructions when applicable.

When the program is run, it detects what instruction sets are supported
and uses only those. My builds currently have 6 code paths in them
that can be run depending on what the CPU supports. It's basically like
having 6 different builds combined into one.

The "baseline code path" uses SSE2, so as long as the CPU supports
at least that, my L101 builds and higher will run. Of course, if SSE2 is
the only instruction set it supports, you may experience very slow
gaming due to old slow CPU

(05-11-2012, 07:39 AM)neobrain Wrote: [ -> ]It won't work if those "special optimized builds" contain any instructions which aren't supported by the CPU. In that case, the program will just crash with an error message IIRC. If you don't get any error even though your CPU doesn't support that instruction set, that basically means the compiler didn't do any special optimizations for AVX and, in turn, that advertising AVX optimizations is kinda stupid.

That's the way my builds *used* to be compiled. I had a separate build
for each type of instruction set. L101 and higher are built with support
for all of the instruction sets listed. If the CPU supports it, it uses it. If not,
it doesn't use it. Either way, my L101 builds and higher should not be
crashing on any computers with a CPU that supports SSE2 or higher,
whether or not they support higher instructions.


I would also like to note that the instruction sets are not the only optimizations
in these builds. The Intel C++ Composer offers a wide array of different
optimizations that can be applied when the code is compiled. While I have tested
and gone through many of them, there are still others I have yet to test.