PureBasic Forums - English

does the compiler create clone code for each processer so when run on amd it will do the 3dnow! instructions and on intel will use sse2 instuctions?
or is it just uses instructions that aren't cpu spcific?

Check the section "Using the command line compiler" in the manual

PB manual wrote: /DYNAMICCPU: Creates a executable containing all the available processor specific routines. When the program is started, it looks for the processor type and then select the more appropriates routines to use. This makes a bigger executable, but result in the fastest possible program.

To my knowledge there are very few(if any) library commands that come in mmx, 3dnow! optimized versions.

The ASM that the compiler produces itself is to my knowledge only generic ASM.

Pupil wrote:To my knowledge there are very few(if any) library commands that come in mmx, 3dnow! optimized versions.

I made a very few, dealing with encryption. No clue if they work with 3.92 though.

The ASM that the compiler produces itself is to my knowledge only generic ASM.

That is what I know, too.

Does anyone know what DYNAMICCPU actually does? Does it, for example, create 386,486 etc codeblocks and do some internal patching at runtime?


Just curious, is all.

My guess is that a jumptable for the functions in question (for the ones that have CPU specific optimizations) is set up in the init code. This is however only a guess from my side, Fred would know for sure, i hope

That's exaclty as Pupil said (you can see that when using the /COMMENTED code with a function which actually support it (actually there is no internal PB functions which use it, but some user libs could)).

Wondering, if its turned on how will the exe work on lets say non-3dnow cpu's? Will the code that works on all cpu's be included too?

thefool wrote:Wondering, if its turned on how will the exe work on lets say non-3dnow cpu's? Will the code that works on all cpu's be included too?

If you set it to for example MMX and you happen to use some functions that support this, the executable of course won't work on non-MMX processors.

It seems to me like the point of "dynamic" is to include all function sets and then pick the best at runtime. (So then it will of course run on any processor.)

i asked if it just meant that the mmx was included. So the size grew bigger but exe worked on all cpu's as well. Its not all "Of course".... i doubt it will include functions for mmx or 3dnow when using dynamic.

When using dynamic CPU all specialized routines will be included which means a probably bigger exe, but also the fastest possible (as each routine will be used depending of the CPU where the exe is running on).

ok thanks for the clearifytation [a word i just made i think ]

Dynamic CPU should be used more often...

it be a good idea if we could have compiler Constants for these so you could write 3dnow!,SSE,MMX version of certain procedures or parts of code that would be nice

Very interesting.

Agree with Dreglor, perhaps /DYNAMICCPU should be used more often. And incode compiler switches would be useful.

The constants would be a great thing!

You could create Exes for 3DNow!, SSE2 and normal(not optimized) and the create an exe that chooses the fastest one.

I'd just speed up a little more in Loops containing Optimized functions

That'd be great

Dummy: you can already do that, what do you mean exactly ?