Subversion Repositories Kolibri OS

    to overflow from time to time.

    values when used in some logical expressions.

    was incorrectly leaving the data marked as uninitialized. The new fix

    addresses this issue.

    now correctly mark this data as initialized when it is in a different

    addressing space.

    provided to assembler directives like "label", "virtual" or "load".

    the same line.

    specific ill-structured preprocessed lines.

    element when default value for iterating variable was specified.

    in some very specific cases.

    types of relocatable values in some places (like "label" directive).

    fail when assembler had preallocated very large amount of memory.

    incorrectly with negative addresses.

    was manifesting with bases larger than 31-bit.

    relocatable addresses in a reverse order (first substracting/negating

    and then adding the other one).

    virtual block with "org" directive.

    addressing space. This label can the be used with "load" or "store"

    directives to allow operations on bytes in any addressing space,

    not just the current one. This special label is defined by following

    its name with double colon, and can only be used with "load" and

    "store" directive, where address can now be specified in two parts,

    first the adressing space label, then the colon and then the

    address inside that addressing space.

    object format between the 32-bit or 64-bit size.

    of some string instructions ("cmps", "lods", "movs" and "outs") is

    used in long mode. Now it is consistent with optimizations done with

    all the other instructions.

    address expressions to cause an error prematurely during the

    parsing stage.

    FMA4, XOP, MOVBE, BMI, TBM, INVPCID, HLE and RTM instruction sets.

    to be calculated by preprocessor in its arguments.

    "format ELF executable" setting.

    special segments in ELF executables.

    generated with "qword" keyword inside square brackets.

    In such case it contains only the preprocessed source that can be extracted

    with PREPSRC tool. If error occured during preprocessing, only the source up

    to the point of error is provided.

    state from the final assembly pass.

    context of formatter directives, and thus are no longer disallowed as

    labels.

    symbol followed by value after the argument name in definition.

    to test whether two values differ only by a constant and not relocatable

    amount.

    calculations in signed and unsigned ranges in full 64-bit. This fixes

    a number of issues - the overflow will now be correctly detected for

    64-bit values in cases, where previous versions could not distinguish

    whether it was an overflow or not. The effect of these corrections is

    that "dq" directive will now behave consistently with behavior of the

    data directives for smaller sizes, and the same applies to all the

    places where "qword" size for value is used.

    64-bit variants of respective instructions.

    mnemonics to allow choosing between 16-bit and 32-bit variants of

    structures used by the "fstenv", "fsave" and "frstor" instructions.

    added "static" keyword for the "public" directive.

    should be used, depending on whether the fixups directory is placed

    somewhere into executable by programer, or not. This makes possible the

    more flexible use of the addressing symbols in case of PE executable fixed

    at some position.

    64-bit object formats and PE executable. This makes some specific

    instructions compilable, but it also forces linker to put such

    generated code into the low 2 gigabytes of addressing space.

    The symbol escaping now has always the higher priority than symbol conversion,

    and both have higher precedence than concatenation.

    placed at the end of the "format" directive line.

    is no longer allowed.

    to help improve long numbers readability.

    various kinds of information from it.

    the same kind as "equ" directive, however there's an important difference

    that "define" doesn't process symbolic constants in the value before

    assigning it. For example:

        a equ a+a

        define b b+b

    value "b+b". This directive may be useful in some advanced

    macroinstructions.

    for slightly better performance and lesser memory usage by assembler.

    The logical values defined with "eq", "eqtype" and "in" operators are now

    evaluated by the parser and if they are enough to determine the condition,

    the whole block is processed accordingly. Thus this block:

                nop

        end if

    that the condition is true, even though one of the logical values makes no

    sense - but since this is none of the "eq", "eqtype" and "in" expressions,

    the parser doesn't investigate.

    needs to determine the condition. So this block:

    versions. This is because after checking that "defined alpha" is false

    condition it doesn't need to know the second logical value to determine the

    value of conjunction.

    obsolete and no longer correct - use "jmp short" instead.

    displacement - now it applies to the size of target address.

    unless you force using the 16-bit immediate with "word" operator.

    when making position-independent code for shared libraries. For any label

    you can get its offset relative to GOT by preceding it with "rva" operator

    (the same keyword as for PE format is used, to avoid adding a new one,

    while this one has very similar meaning).

    to make the distinction between the run-time segments and linkable

    sections. If you had a "section" directive in your ELF executables and they

    no longer assemble, replace it with "segment".

    even when there are no fixups to be put there (in such case it creates the

    directory with one empty block).

    possibility of making extensive symbol dumps.

    prioritized constant.

    string it simply does nothing. Thus the sequence of ` operators applied to

    one symbol work the same as if there was just one. In similar manner, the

    sequence of # operators now works as if it was a single one - using such a

    sequence instead of escaping, which was kept for some backward

    compatibility, is now deprecated.

    incorrectly interpreted as data definition).

    setting).

    must always fit in the range of signed 64 integer now.

    as a second addressing register - fixed.

    wrongly signaled - fixed.

    (with "format MS64 COFF" setting).

    label.

    than one resource of the same string name, the separate resource

    directories were created with the same names - fixed.

    macros to be processed the wrong way.