Correct, there is one last remaining thing I want sorted before I can do the release builds, FYI here is the list of changes for 2.50:
Fix vmovdqu encoding, moved to new CodeGen.
Fix listing .listmacro
Fix movd/q encodings.
Prevent option stackbase rsp: with elf64 for now.
Dont optimise prologues based on hasInvoke, this is completely removed as it prevent libraries or code without visible invokes from generating correctly.
Prevent FPO based purely on USES.
Improve win64:0/1 lower modes compatibility and prologue generation.
Add option support to allow WIN64 procedures to not affect flags in epilogue.
Include W.I.P. codegen v2 files in repository
Fix encoding of SIB with vctsi2ss
Allow REP prefix on REPxx instructions without needing M510 compatibility.
Allow type size specifiers on immediate->memory operations
Improved consistency of SSE/AVX opcode selection for OPTION ARCH
Added new RawInterface and stdfunc types
Add support for \r \n and \t to unicode string literals
Ensure Arch SSE is the default
Ensure @Arch variable correctly reflects Arch setting (affected macro library items like LOADSS)
Fixed two bugs when using C-style HLL calls (using any TYPE PTR paramter and case sensitivity issue in 32bit)
Fixed undeclared identifier causing uasm to hang
More updates for CodegenV2
Fixed listing file delimiter issue on Windows
Unicode/Wide character string declarations would crash Uasm when split over multiple lines
Update Linux Makefile (GccLinux64.mak)
Improved BSS Data warnings for BIN files
Fixed LOADPS macro library function
Improved byte/word immediate to memory sizing coercion in codegen.
Fixed a parser bug preventing negative numbers greater than a byte from warning when used with a byte reg or mem location.
The one remaining thing I want is as mentioned in another thread, preventing generating of useless relocations in COFF when RIP referencing items in .code.. I'm still mulling this one, as it would be really nice to have a generic rip-relative method to address anything, IE: make the entire code position independant however I don't think under Windows this is possible as you have no guarantee about the positions/address of the sections in memory (someone correct me if' i'm wrong) however for the code section in which the LEA exists it should always be safe.