Index
> Main > What's new in fasm 1.53? |
| Author |
|
|
vst
What's new in fasm 1.53
 |
|||
14 Jul 2004, 12:45 |
|
|
vid
i still can't discover what's new in new proceure macros except "endp" macros.
|
|||
|
14 Jul 2004, 18:51 |
|
|
VitalOne
You don't have to use "enter" anymore in procs if it's not needed.
|
|||
|
14 Jul 2004, 21:27 |
|
|
decard
and you can have more than one "return" macros in your proc.
|
|||
|
15 Jul 2004, 08:00 |
|
|
fasm9
7-20-2004 new FASM 1.53 version released.
What's new in re-version? --  |
|||
|
21 Jul 2004, 00:14 |
|
|
Tomasz Grysztar
Only fix for a bug with ELF executable section addressing, see http://board.flatassembler.net/topic.php?t=1877
|
|||
|
21 Jul 2004, 07:55 |
|
|
Tomasz Grysztar
Another small update, also whatsnew.txt has been updated this time.
The new feature is that floating point values can be used as address fields now. Though it appears to be completely useless (who would need an instruction like "mov eax,[1.0]"?), it fixes the problem with using floating point values as an arguments to extended "invoke" with win32ax includes (where "pushd" macro is used). |
|||
|
22 Jul 2004, 09:51 |
|
|
vid
can't it be really done another way? How can be interpreted result of "mov eax,[1.0]", as "mov eax,[1]" (what is "mov eax,[1.5]" then?) or as "mov eax,[binary_representation_of_floating_1]"?
|
|||
|
22 Jul 2004, 19:03 |
|
|
Tomasz Grysztar
Of course as "mov eax,[binary_32_bit_representation_of_floating_1]" - this should be obvious when considering fasm's literality, just compare
Code: mov eax,1 mov eax,[1] and Code: mov eax,1.0 mov eax,[1.0] |
|||
|
22 Jul 2004, 19:09 |
|
|
pelaillo
Could you give an example of application of [1.0]
|
|||
|
22 Jul 2004, 20:44 |
|
|
Tomasz Grysztar
As I wrote few posts above, it's completely useless, but makes fasm's syntax more "complete" and fixes one macro problem.
|
|||
|
22 Jul 2004, 20:54 |
|
|
fasm9
Privalov wrote: it fixes the problem with using floating point values as an arguments to extended "invoke" with win32ax includes (where "pushd" macro is used). Does this patch also apply to Linux FASM source code? i am afraid Floating address cause another hidden/potential bugs. |
|||
|
22 Jul 2004, 21:10 |
|
|
Tomasz Grysztar
Quote: i am afraid Floating address cause another hidden/potential bugs. It's cannot interfere with any other code, the words that are floating point values cannot be used for any other purpose in FASM. |
|||
|
22 Jul 2004, 21:14 |
|
|
Madis731
Not *completely* useless because it would be tedious to use:
Code: mov eax,[3F800000h] ;or maybe mov ebx,3FC00000h I would prefer these 
Code: mov eax,[1.0] mov ebx,1.5 |
|||
|
23 Jul 2004, 10:54 |
|
|
Tomasz Grysztar
Talk about obfuscated code...
 |
|||
|
23 Jul 2004, 11:47 |
|
< Last Thread | Next Thread > |
Forum Rules:
|