flat assembler
Message board for the users of flat assembler.
![]() |
What's the fastest/better? | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Total Votes : 3 |
Author |
|
HaHaAnonymous 27 Sep 2013, 00:52
[ Post removed by author. ]
Last edited by HaHaAnonymous on 28 Feb 2015, 19:49; edited 1 time in total |
|||
![]() |
|
A$M 27 Sep 2013, 01:39
HaHaAnonymous wrote: I doubt this poll will result in anything good. There are too many options. Thanks for your answer. (my processor can run SSE4 ![]() |
|||
![]() |
|
revolution 27 Sep 2013, 04:36
The standard answer to "which is faster" is: we don't know, there are too many variables. When you look at only the instructions executing you get a very small view of what is happening in the system as a whole. Things like cache management might be more important, or not. Things like code layout and latency values might be more important, or not. Things like RAM timings and numbers of channels might be more impotant, or not. Things like which OS or GPU or even your cooling fan capability can affect the run speed of code, thses might be more important, or not. Like HaHaAnonymous mentions above, it depends upon your precise situation as to which code will be faster.
|
|||
![]() |
|
edfed 27 Sep 2013, 20:45
the speed of your code is also the speed of the writing of the code. and as the writing speed is a very variable time, you can just try to determine the method where your writing is faster, and then, see what is the benefit to try anything else.
i think, when talking about Fixed and floating points, the fixed is very good and fast, but floating is also good and fast, it always depends on the dynamics of your signals. if you should only cover a little count of digits, you should maybe use fixed point. if you should manage values from nano to giga, maybe the floating point is better. maybe none of them can suit your requirement, and then, you'll need a sort of bigDecimal type to define values with more than 19 decimal digits. |
|||
![]() |
|
< Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2025, Tomasz Grysztar. Also on GitHub, YouTube.
Website powered by rwasa.