Hi all,
With a big thanks to Habran for his immense efforts I'd like to share with you all the release of HJWasm 2.13pre.
There is a huge list of new features and improvements over JWasm and previous interim HJWasm posts:
- Added support for AVX512F, ZMM registers and EVEX encoding.
- RIP register support.
- .FOR high level macro support and enhancements.
- MOVQ and VMOVQ to supplement MOVD and bring instructions in line with Intel and AMD reference guides.
- Fixed bug requiring the use of xmmword ptr and ymmword ptr.
- Additional unsigned flag comparison predicates added for HLL syntax (ABOVE,BELOW)
- Removed warnings relating to alignment by 32 (as this is a requirement for AVX vectors), leads to clean builds.
- New instructions added: RDRAND, RDSEED, F16C(VCVTPH2PS, VCVTPS2PH)
- VEX encoded general purpose instructions added ANDN, MULX, FMA, BMI and more...
- Support for more optimised stack and invoke usage as well as stack alignment and RSP stack base.
http://www.terraspace.co.uk/hjwasm.html (http://www.terraspace.co.uk/hjwasm.html) is the new home for binary image downloads, as well as a home for h2incx and wininc.
Source code will be available and maintained in a git repo on bitbucket once all feedback and testing is complete and we're satisfied the version is completely stable.
Enjoy!
John / Habran
:icon14: :t
Thanks for your job and thanks to share it.
This morning I replaced JWasm with he new HJWasm64 version.
Yestirday I had no error when compiling,
This morning it gaves errors for the following include files :
Quoteindows.inc
SECURITY_NULL_SID_AUTHORITY equ {0,0,0,0,0,0}
SECURITY_WORLD_SID_AUTHORITY equ {0,0,0,0,0,1}
SECURITY_LOCAL_SID_AUTHORITY equ {0,0,0,0,0,2}
SECURITY_CREATOR_SID_AUTHORITY equ {0,0,0,0,0,3}
SECURITY_NON_UNIQUE_AUTHORITY equ {0,0,0,0,0,4}
SECURITY_CREATOR_OWNER_SERVER_RID equ (00000002h)
SECURITY_CREATOR_GROUP_SERVER_RID equ (00000003h)
SECURITY_NT_AUTHORITY equ {0,0,0,0,0,5}
SYSTEM_LUID equ { 3E7h, 0h }
ANONYMOUS_LOGON_LUID equ { 3e6h, 0h }
Winextra.inc
MAPI_ONE_OFF_UID equ { 81h, 2bh, 1fh, 0a4h, 0beh, 0a3h, 10h, 19h,09dh, 6eh, 0h, 0ddh, 01h, 0fh, 54h, 02h }
MAPI_ONE_OFF_UID equ { 81h, 2bh, 1fh, 0a4h, 0beh, 0a3h, 10h, 19h,09dh, 6eh, 0h, 0ddh, 01h, 0fh, 54h, 02h }
My command line :
QuoteC:\JWasm\Bin\JWASM.EXE -9 -Fl -c -zlf -zlp -zls -W3 -coff -Cp -nologo /I"C:\JWasm\Include" "ASD.asm"
I transformed the line to comment and no problem but there is work for you I think.
Merci beaucoup
Thanks for reporting Grincheux :t
It happened because of EVEX {sae}
Fixed version will be uploaded in a few hours
Please test it :biggrin:
Builds fine with (almost) all assemblers ;)
include \masm32\include\masm32rt.inc ; plain Masm32 for the fans of pure assembler
.code
minput MOUSEINPUT <>
start: print "Hello World"
exit
end start
QuoteC:\JWasm\Bin\JWASM.EXE -9 -Fl -c -zlf -zlp -zls -W3 -coff -Cp -nologo /I"C:\JWasm\Include" "ASD.asm"
***********
ASCII build
***********
\masm32\include\Windows.inc(20234) : Error A2209: Syntax error: 0,0,0,0,0,0
\masm32\include\Windows.inc(20234): Included by
ASD.inc(3): Included by
ASD.asm(6): Main line code
\masm32\include\Windows.inc(20235) : Error A2209: Syntax error: 0,0,0,0,0,1
\masm32\include\Windows.inc(20235): Included by
ASD.inc(3): Included by
ASD.asm(6): Main line code
\masm32\include\Windows.inc(20236) : Error A2209: Syntax error: 0,0,0,0,0,2
\masm32\include\Windows.inc(20236): Included by
ASD.inc(3): Included by
ASD.asm(6): Main line code
\masm32\include\Windows.inc(20237) : Error A2209: Syntax error: 0,0,0,0,0,3
\masm32\include\Windows.inc(20237): Included by
ASD.inc(3): Included by
ASD.asm(6): Main line code
\masm32\include\Windows.inc(20238) : Error A2209: Syntax error: 0,0,0,0,0,4
\masm32\include\Windows.inc(20238): Included by
ASD.inc(3): Included by
ASD.asm(6): Main line code
\masm32\include\Windows.inc(20241) : Error A2209: Syntax error: 0,0,0,0,0,5
\masm32\include\Windows.inc(20241): Included by
ASD.inc(3): Included by
ASD.asm(6): Main line code
\masm32\include\Windows.inc(20254) : Error A2209: Syntax error: 3E7h, 0h
\masm32\include\Windows.inc(20254): Included by
ASD.inc(3): Included by
ASD.asm(6): Main line code
\masm32\include\Windows.inc(20255) : Error A2209: Syntax error: 3e6h, 0h
\masm32\include\Windows.inc(20255): Included by
ASD.inc(3): Included by
ASD.asm(6): Main line code
\masm32\include\winextra.inc(3959) : Error A2209: Syntax error: 81h, 2bh, 1fh, 0a4h, 0beh, 0a3h, 10h, 19h,09dh, 6eh, 0h, 0ddh, 01h, 0fh, 54h, 02h
\masm32\include\winextra.inc(3959): Included by
\masm32\include\Windows.inc(26889): Included by
ASD.inc(3): Included by
ASD.asm(6): Main line code
\masm32\include\winextra.inc(4111) : Error A2209: Syntax error: 098h, 15h, 0ACh, 08h, 0AAh, 0B0h, 10h, 1Ah,8Ch, 093h, 08h, 0h, 2Bh, 2Ah, 56h, 0C2h
\masm32\include\winextra.inc(4111): Included by
\masm32\include\Windows.inc(26889): Included by
ASD.inc(3): Included by
ASD.asm(6): Main line code
Utils.asm(86) : Warning A4265: Procedure argument or local not referenced: _hWnd
Utils.asm(86): Included by
ASD.inc(97): Included by
ASD.asm(6): Main line code
Disassembly_Dlg.asm(43) : Warning A4265: Procedure argument or local not referenced: __hWnd
Disassembly_Dlg.asm(43): Included by
ASD.inc(99): Included by
ASD.asm(6): Main line code
Disassembly_Dlg.asm(100) : Warning A4265: Procedure argument or local not referenced: __lParam
Disassembly_Dlg.asm(100): Included by
ASD.inc(99): Included by
ASD.asm(6): Main line code
Disassembly_Dlg.asm(109) : Warning A4265: Procedure argument or local not referenced: _szTmp
Disassembly_Dlg.asm(109): Included by
ASD.inc(99): Included by
ASD.asm(6): Main line code
ASD.asm(315) : Warning A4265: Procedure argument or local not referenced: __cmdshow
ASD.asm(315) : Warning A4265: Procedure argument or local not referenced: __lpszCmdline
ASD.asm(315) : Warning A4265: Procedure argument or local not referenced: __hPrevInstance
ASD.asm: 353 lines, 1 passes, 203 ms, 7 warnings, 10 errors
Make error(s) occured.
Total compile time 312 ms
Hi,
New binaries are uploaded onto the site which include the fix for types declared with { }
Regards,
John
Hi,
Binary packages have been updated again and the "pre" status removed. From our testing all appears to be in order but we shall await the final feedback from users / forum members to confirm that we're all happy with this release. Upon this milestone we will publish all source code and update the Git repository and supply relevant links / updated docs.
Cheers!
John
Same as before with version 19 January.
Quote from: jj2007 on January 16, 2016, 09:58:25 PM
Builds fine with (almost) all assemblers ;)
include \masm32\include\masm32rt.inc ; plain Masm32 for the fans of pure assembler
.code
minput MOUSEINPUT <>
start: print "Hello World"
exit
end start
The problem is here, and it's a known problem. Of course, it's not a problem if you can convince several hundred forum members to modify their Windows.inc, and adjust their existing sources (4,000+ in my case) accordingly ;)
line 12948:
MOUSEINPUT STRUCT
_dx DWORD ?
dy DWORD ?
mouseData DWORD ?
dwFlags DWORD ?
time DWORD ?
dwExtraInfo DWORD ?
MOUSEINPUT ENDS
line 19062:
NMLVSCROLL STRUCT
hdr NMHDR <>
_dx DWORD ?
dy DWORD ?
NMLVSCROLL ENDS
deleted
I've just double checked the archive and dumpbin'ed the executable image:
D:\HJWasm\hjwasm213_x86>hjwasm32
HJWasm v2.13.32bit., Jan 17 2016, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
usage: HJWasm [ options ] filelist [@env_var]
Run "HJWasm -?" or "HJWasm -h" for more info
D:\HJWasm\hjwasm213_x86>dumpbin -headers hjwasm32.exe
Microsoft (R) COFF/PE Dumper Version 10.00.40219.01
Copyright (C) Microsoft Corporation. All rights reserved.
Dump of file hjwasm32.exe
PE signature found
File Type: EXECUTABLE IMAGE
FILE HEADER VALUES
14C machine (x86)
5 number of sections
569B245E time date stamp Sun Jan 17 05:19:26 2016
0 file pointer to symbol table
0 number of symbols
E0 size of optional header
102 characteristics
Executable
32 bit word machine
OPTIONAL HEADER VALUES
10B magic # (PE32)
12.00 linker version
4F200 size of code
2D200 size of initialized data
0 size of uninitialized data
41D81 entry point (00441D81)
1000 base of code
51000 base of data
400000 image base (00400000 to 00480FFF)
1000 section alignment
200 file alignment
6.00 operating system version
0.00 image version
6.00 subsystem version
0 Win32 version
Could it be antivirus possibly? Which version of Windows are you running?
mov Byte Ptr [1234h],clQuoteError A2049: Invalid instruction operands
But this one
Quotemov cl,Byte Ptr [1234h]
is OK!
I don't understand why?
Habran could you check out the dy issue again,
It shouldn't cause a problem anymore JJ2007, we had agreed to remove that (based on a previous thread) in favour of using equates if required. So it might just have been missed somewhere, we'll sort it out :)
Quote from: Grincheux on January 20, 2016, 02:44:37 AM
mov Byte Ptr [1234h],cl
QuoteError A2049: Invalid instruction operands
But this one Quotemov cl,Byte Ptr [1234h]
is OK!
I don't understand why?
Is this in a 32bit or 64bit application?
deleted
Quote from: Grincheux on January 20, 2016, 02:44:37 AM
mov Byte Ptr [1234h],cl
QuoteError A2049: Invalid instruction operands
But this one Quotemov cl,Byte Ptr [1234h]
is OK!
I don't understand why?
standard MASM syntax would be to add a segment override operator
mov ds:[1234h],cl
I'm testing on an x64 Windows 7 machine. I will try setup a 32bit vm and test there. I'm also trying to get the "download warning" removed.. somehow without paying a fortune to sign the archive.
Quote from: jj2007 on January 20, 2016, 01:24:20 AM
Same as before with version 19 January.
Quote from: jj2007 on January 16, 2016, 09:58:25 PM
Builds fine with (almost) all assemblers ;)
include \masm32\include\masm32rt.inc ; plain Masm32 for the fans of pure assembler
.code
minput MOUSEINPUT <>
start: print "Hello World"
exit
end start
The problem is here, and it's a known problem. Of course, it's not a problem if you can convince several hundred forum members to modify their Windows.inc, and adjust their existing sources (4,000+ in my case) accordingly ;)
line 12948:
MOUSEINPUT STRUCT
_dx DWORD ?
dy DWORD ?
mouseData DWORD ?
dwFlags DWORD ?
time DWORD ?
dwExtraInfo DWORD ?
MOUSEINPUT ENDS
line 19062:
NMLVSCROLL STRUCT
hdr NMHDR <>
_dx DWORD ?
dy DWORD ?
NMLVSCROLL ENDS
Just re-tested this using the standard windows.inc file from masm32 package (which has DY in) and it assembles fine for me, no warnings about the use of DY.
What error do you get ?
Quotestandard MASM syntax would be to add a segment override operator
Yes but CS, DS and ES = 0 so it is not obliged. The processor ignores these overides.
The only overides that are not 0 are FS and GS.
In the other sens I don't need a segment overide!
\masm32\include\windows.inc(12948) : Error A2209: Syntax error:
\masm32\include\windows.inc(12948): Included by
\masm32\include\masm32rt.inc(38): Included by
Tmp_File.asm(1): Main line code
\masm32\include\windows.inc(19062) : Error A2209: Syntax error:
\masm32\include\windows.inc(19062): Included by
\masm32\include\masm32rt.inc(38): Included by
Tmp_File.asm(1): Main line code
Tmp_File.asm(4) : Error A2209: Syntax error:
JWasm, asmc and the ML family have no problems.
Quote from: Grincheux on January 20, 2016, 04:44:12 AM
Quotestandard MASM syntax would be to add a segment override operator
Yes but CS, DS and ES = 0 so it is not obliged. The processor ignores these overides.
The only overides that are not 0 are FS and GS.
In the other sens I don't need a segment overide!
it must be explicit when an absolute address is given
the DS: override is not coded, but the assembler requires it
try it :P
another way is to create a label
ORG 1234h
SomeLabel LABEL BYTE
;
;
;
mov SomeLabel,cl
johnsa, habran,
it looks like that you are currently focusing on adding new feature, however, I'm curious what are your plans on the open bug reports found at sourceforge?
I've also noted that HJwasm comes with an old build of JWASM: will be there any development on JWASM, means HJWASM as branch of JWASM?
regards
Hi :biggrin:
>Grincheux, Dave is correct, this is not a bug, just an inappropriate usage of the assembler.
>jj2007, I don't know why you have that problem because I tested examples from masm32 with original windows.inc and they built flawlessly.
>nidud, I will build 32 binaries with MingW and post it here for you to test
>qWord, we are not going to work on JWasm any more, therefore we are not going to fix bugs on it.
HJWasm is from now our concern and soon we will upload the source on the Teraspace. I will discus with Johnsa how we will organize bug reports
Cheers!
Here is a CodeBlock 32 bit build
I have replaced it with VS13 build because it was not working as expected
deleted
Quote from: habran on January 20, 2016, 08:45:49 AM
>jj2007, I don't know why you have that problem because I tested examples from masm32 with original windows.inc and they built flawlessly.
With HJWasm /nologo /c /coff /Fl /Sn for a hello world, I get these errors.
- Windows.inc is 977412 bytes of 10.01.2012 00:21:10
- HJWasm is 459776 bytes of 17.01.2016 06:19:26
Do you use a specific command line switch? Anybody else able to build this hello world with HJWasm?
include \masm32\include\masm32rt.inc
.code
start:
inkey "Hello World"
exit
end start
Hi!
A lot of time compiling only console little programs and little pieces from forum discussions, and what I found now it's that more complex code (but a simple ObjAsm32 object) only work with JWasm 2.11 or ML .
Obviously I erase or change something because 4 month ago JWasm 2.13 work fine, but now JWam 2.13 or HJWasm32 don't work!
A couple of hours later I remember the collision with the ".for" macro in ObjAsm32 (that need to be commented or uncommented, depends on compiler).
I'm expecting the source for to change the leng of lines and max nested macros :t.
Regards.
Hi Jochen!!
\foro\jj\hjw>hjwasm32 -c -coff hello.asm
HJWasm v2.13.32bit., Jan 17 2016, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
***********
ASCII build
***********
hello.asm: 8 lines, 2 passes, 296 ms, 0 warnings, 0 errors
\foro\jj\hjw>link /subsystem:console hello.obj
Microsoft (R) Incremental Linker Version 5.12.8078
Copyright (C) Microsoft Corp 1992-1998. All rights reserved.
\foro\jj\hjw>hello
Hello World
HJWasm is 64 bit.
Thanks HSE :t
>jj2007, are you sure that you are using the newest HJWasm, please check command outpt
>nidud, can you please post me the sources you have tested
>HSE if you are using .for - .endfor please pay attention, in HJWasm we changed a delimeter to ':' instead of '¦' from before, that is because in debugger mode isspace() was stumbling on '¦'
HJWasm must use '()' brackets otherwise will not work, also, '++' or '--' must come after the variable not before,so
eax++ works, eax-- works but ++eax or --eax doesn't
so, here is one example:
.for (:WORD PTR[rcx]:rcx+=2,rdx+=2)
mov ax,[rcx]
.if (ax != WORD PTR[rdx])
.if (ax > WORD PTR[rdx])
mov eax,1
.else
mov eax,-1
.endif
jmp aexit
.endif
.endfor
another one:
.for (::)
.if (WPTR[rax] == 0)
.break .if (WPTR[rax+2] == 0) ;//break if the last char
inc r8d ;//increase the counter
.endif
add rax,2 ;//word character = 2 bytes
.endfor
and one more:
.for (ebp=0:ebp<ebx:ebp++)
movsxd rax,ci.nCharInLine
mov rcx,ci.lpLine
mov rcx,[rcx].SOMEDATA.wLine
.if (WPTR[rcx+rax*2] == 9)
mov eax,r13d
cdq
idiv nTabStop
mov eax,nTabStop
sub eax,edx
add r13d,eax
.else
inc r13d
.endif
.break .if (!qwinvoke(NextChar,ADDR ci))
.endfor
deleted
Quote from: habran on January 20, 2016, 02:27:33 PM
>jj2007, are you sure that you are using the newest HJWasm, please check command outpt
Mystery solved, I had used HJWasm instead of HJWasm
32 :(
Sorry...
Where can I find a version of JWAsm that compiles without false errors
I always have the same errors:
QuoteC:\JWasm\Bin\JWASM.EXE -9 -Fl -c -zlf -zlp -zls -W3 -coff -Cp /I"C:\JWasm\Include" "ASD.asm"
HJWasm v2.13.64bit.pre, Jan 14 2016, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
***********
ASCII build
***********
\masm32\include\Windows.inc(20234) : Error A2209: Syntax error: 0,0,0,0,0,0
\masm32\include\Windows.inc(20234): Included by
ASD.inc(4): Included by
ASD.asm(6): Main line code
\masm32\include\Windows.inc(20235) : Error A2209: Syntax error: 0,0,0,0,0,1
\masm32\include\Windows.inc(20235): Included by
ASD.inc(4): Included by
ASD.asm(6): Main line code
\masm32\include\Windows.inc(20236) : Error A2209: Syntax error: 0,0,0,0,0,2
\masm32\include\Windows.inc(20236): Included by
ASD.inc(4): Included by
ASD.asm(6): Main line code
\masm32\include\Windows.inc(20237) : Error A2209: Syntax error: 0,0,0,0,0,3
\masm32\include\Windows.inc(20237): Included by
ASD.inc(4): Included by
ASD.asm(6): Main line code
\masm32\include\Windows.inc(20238) : Error A2209: Syntax error: 0,0,0,0,0,4
\masm32\include\Windows.inc(20238): Included by
ASD.inc(4): Included by
ASD.asm(6): Main line code
\masm32\include\Windows.inc(20241) : Error A2209: Syntax error: 0,0,0,0,0,5
\masm32\include\Windows.inc(20241): Included by
ASD.inc(4): Included by
ASD.asm(6): Main line code
\masm32\include\Windows.inc(20254) : Error A2209: Syntax error: 3E7h, 0h
\masm32\include\Windows.inc(20254): Included by
ASD.inc(4): Included by
ASD.asm(6): Main line code
\masm32\include\Windows.inc(20255) : Error A2209: Syntax error: 3e6h, 0h
\masm32\include\Windows.inc(20255): Included by
ASD.inc(4): Included by
ASD.asm(6): Main line code
\masm32\include\winextra.inc(3959) : Error A2209: Syntax error: 81h, 2bh, 1fh, 0a4h, 0beh, 0a3h, 10h, 19h,09dh, 6eh, 0h, 0ddh, 01h, 0fh, 54h, 02h
\masm32\include\winextra.inc(3959): Included by
\masm32\include\Windows.inc(26889): Included by
ASD.inc(4): Included by
ASD.asm(6): Main line code
\masm32\include\winextra.inc(4111) : Error A2209: Syntax error: 098h, 15h, 0ACh, 08h, 0AAh, 0B0h, 10h, 1Ah,8Ch, 093h, 08h, 0h, 2Bh, 2Ah, 56h, 0C2h
\masm32\include\winextra.inc(4111): Included by
\masm32\include\Windows.inc(26889): Included by
ASD.inc(4): Included by
ASD.asm(6): Main line code
Utils.asm(86) : Warning A4265: Procedure argument or local not referenced: _hWnd
Utils.asm(86): Included by
ASD.inc(216): Included by
ASD.asm(6): Main line code
Cpu.asm(703) : Warning A4265: Procedure argument or local not referenced: __hWnd
Cpu.asm(703): Included by
ASD.inc(217): Included by
ASD.asm(6): Main line code
ASD_Exit.asm(133) : Warning A4265: Procedure argument or local not referenced: __lParam
ASD_Exit.asm(133): Included by
ASD.inc(219): Included by
ASD.asm(6): Main line code
Disassembly_Dlg.asm(597) : Warning A4265: Procedure argument or local not referenced: __lParam
Disassembly_Dlg.asm(597): Included by
ASD.inc(220): Included by
ASD.asm(6): Main line code
Disassembly.asm(254) : Warning A4265: Procedure argument or local not referenced: _lpszRegister
Disassembly.asm(254): Included by
ASD.inc(222): Included by
ASD.asm(6): Main line code
ASD.asm(429) : Warning A4265: Procedure argument or local not referenced: __cmdshow
ASD.asm(429) : Warning A4265: Procedure argument or local not referenced: __lpszCmdline
ASD.asm(429) : Warning A4265: Procedure argument or local not referenced: __hPrevInstance
ASD.asm: 473 lines, 1 passes, 337 ms, 8 warnings, 10 errors
Make error(s) occured.
Total compile time 421 ms
------------- Where can I find a version of JWAsm that compiles without false errors ? ----------------------
http://masm32.com/board/index.php?topic=4256.msg45375#msg45375
must have an older windows.inc file
mine shows for position 20234 onward:
SUBLANG_URDU_PAKISTAN equ 01h
SUBLANG_URDU_INDIA equ 02h
SUBLANG_UZBEK_LATIN equ 01h
SUBLANG_UZBEK_CYRILLIC equ 02h
Quote from: Grincheux on January 21, 2016, 02:34:26 AM
Where can I find a version of JWAsm that compiles without false errors
I always have the same errors:
QuoteC:\JWasm\Bin\JWASM.EXE -9 -Fl -c -zlf -zlp -zls -W3 -coff -Cp /I"C:\JWasm\Include" "ASD.asm"
HJWasm v2.13.64bit.pre, Jan 14 2016, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
***********
ASCII build
***********
\masm32\include\Windows.inc(20234) : Error A2209: Syntax error: 0,0,0,0,0,0
\masm32\include\Windows.inc(20234): Included by
ASD.inc(4): Included by
ASD.asm(6): Main line code
\masm32\include\Windows.inc(20235) : Error A2209: Syntax error: 0,0,0,0,0,1
\masm32\include\Windows.inc(20235): Included by
ASD.inc(4): Included by
ASD.asm(6): Main line code
\masm32\include\Windows.inc(20236) : Error A2209: Syntax error: 0,0,0,0,0,2
\masm32\include\Windows.inc(20236): Included by
ASD.inc(4): Included by
ASD.asm(6): Main line code
\masm32\include\Windows.inc(20237) : Error A2209: Syntax error: 0,0,0,0,0,3
\masm32\include\Windows.inc(20237): Included by
ASD.inc(4): Included by
ASD.asm(6): Main line code
\masm32\include\Windows.inc(20238) : Error A2209: Syntax error: 0,0,0,0,0,4
\masm32\include\Windows.inc(20238): Included by
ASD.inc(4): Included by
ASD.asm(6): Main line code
\masm32\include\Windows.inc(20241) : Error A2209: Syntax error: 0,0,0,0,0,5
\masm32\include\Windows.inc(20241): Included by
ASD.inc(4): Included by
ASD.asm(6): Main line code
\masm32\include\Windows.inc(20254) : Error A2209: Syntax error: 3E7h, 0h
\masm32\include\Windows.inc(20254): Included by
ASD.inc(4): Included by
ASD.asm(6): Main line code
\masm32\include\Windows.inc(20255) : Error A2209: Syntax error: 3e6h, 0h
\masm32\include\Windows.inc(20255): Included by
ASD.inc(4): Included by
ASD.asm(6): Main line code
\masm32\include\winextra.inc(3959) : Error A2209: Syntax error: 81h, 2bh, 1fh, 0a4h, 0beh, 0a3h, 10h, 19h,09dh, 6eh, 0h, 0ddh, 01h, 0fh, 54h, 02h
\masm32\include\winextra.inc(3959): Included by
\masm32\include\Windows.inc(26889): Included by
ASD.inc(4): Included by
ASD.asm(6): Main line code
\masm32\include\winextra.inc(4111) : Error A2209: Syntax error: 098h, 15h, 0ACh, 08h, 0AAh, 0B0h, 10h, 1Ah,8Ch, 093h, 08h, 0h, 2Bh, 2Ah, 56h, 0C2h
\masm32\include\winextra.inc(4111): Included by
\masm32\include\Windows.inc(26889): Included by
ASD.inc(4): Included by
ASD.asm(6): Main line code
Utils.asm(86) : Warning A4265: Procedure argument or local not referenced: _hWnd
Utils.asm(86): Included by
ASD.inc(216): Included by
ASD.asm(6): Main line code
Cpu.asm(703) : Warning A4265: Procedure argument or local not referenced: __hWnd
Cpu.asm(703): Included by
ASD.inc(217): Included by
ASD.asm(6): Main line code
ASD_Exit.asm(133) : Warning A4265: Procedure argument or local not referenced: __lParam
ASD_Exit.asm(133): Included by
ASD.inc(219): Included by
ASD.asm(6): Main line code
Disassembly_Dlg.asm(597) : Warning A4265: Procedure argument or local not referenced: __lParam
Disassembly_Dlg.asm(597): Included by
ASD.inc(220): Included by
ASD.asm(6): Main line code
Disassembly.asm(254) : Warning A4265: Procedure argument or local not referenced: _lpszRegister
Disassembly.asm(254): Included by
ASD.inc(222): Included by
ASD.asm(6): Main line code
ASD.asm(429) : Warning A4265: Procedure argument or local not referenced: __cmdshow
ASD.asm(429) : Warning A4265: Procedure argument or local not referenced: __lpszCmdline
ASD.asm(429) : Warning A4265: Procedure argument or local not referenced: __hPrevInstance
ASD.asm: 473 lines, 1 passes, 337 ms, 8 warnings, 10 errors
Make error(s) occured.
Total compile time 421 ms
The console output shows your version dated the 14th of January. There was a subsequent update from the 17th which resolved this issue, items declared using {}.
The binary packages are available to download at : http://www.terraspace.co.uk/hjwasm.html (http://www.terraspace.co.uk/hjwasm.html)
In H2INCX.INI x64 reserved words are missing ? Like FRAME ?
H2INCX is supplied "as-is" from Japheth's site so I haven't really looked at any part of it, I don't believe we have source for it either.
Perhaps someone else who has used it more extensively can comment on this? I'm sure it would be possible to just add these missing reserved words to the ini file if it's required. If that is the case and we compile a list of them I'll happily update the ini and archive on our site.
ToutEnMasm, Wake up :biggrin:
The binary packages are available to download at : http://www.terraspace.co.uk/hjwasm.html
Pay atention:HJWasm not JWasm
>JJ2007, I new that 007 is for James Bond :biggrin:
>nidud, thanks, I'll test it
Some timings for building the MasmBasic library:
mlv615 ; 7.0 secs
HJWasm32 ; 6.3 secs
JWasm ; 3.0 secs
asmc ; 2.3 secs
and for the RichMasm editor (>17k lines):
HJWasm32 ; 1.0 secs
JWasm ; 0.8 secs
asmc ; 0.7 secs
QuoteC:\JWasm\Bin\JWASM.EXE -9 -Fl -c -zlf -zlp -zls -W3 -coff -Cp /I"C:\JWasm\Include" "ASD.asm"
HJWasm v2.13.64bit., Jan 17 2016, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
That's OK
deleted
Quote from: jj2007 on January 21, 2016, 06:36:59 AM
Some timings for building the MasmBasic library:
mlv615 ; 7.0 secs
HJWasm32 ; 6.3 secs
JWasm ; 3.0 secs
asmc ; 2.3 secs
and for the RichMasm editor (>17k lines):
HJWasm32 ; 1.0 secs
JWasm ; 0.8 secs
asmc ; 0.7 secs
I wonder if the timings would differ due to the compiler / C library implementation used. Habran do you recall off-hand which compiler/build-chain Japheth used for the Windows versions?
I can't think that the changes added thus far would slow the build down that much, apart from some extra keywords to lookup against in the tokenisation phase.
Quote from: nidud on January 21, 2016, 07:27:02 AMJJ, assuming the test is done on a 64-bit OS could you run a test to see if there is any difference between the 32 and 64-bit version?
RichMasm source:
HJWasm32 ; 1000 ms
HJWasm64 ; 920 ms
JWasm ; 858 ms
asmc ; 733 msThe library builds in 5.2 seconds instead of 6.3 for HJWasm32.
Btw I use AsmC for my long sources now, especially for testing the library. Two seconds instead of six makes a big difference. But still, I could imagine that AsmC could become faster by using some of the well-tested bread & butter algos, such as MB Len() and Instr_(FAST, ...).
Quote from: johnsa on January 21, 2016, 08:18:51 AM... some extra keywords to lookup against in the tokenisation phase.
Have a look at this C++ std::map case-insensitive 'find' (http://masm32.com/board/index.php?topic=5048.msg54257#msg54257) post. Still work in progress, but it's blazing fast already.
Quote from: nidud on January 21, 2016, 07:27:02 AM
I tested the 64-bit version with the same result so it's not 32/64-bit issue. This is the files not deleted from the TMP directory:
.. DATA7 err OFFSET6 err
ENDIAN BIN DLL64 err OPATTR6 err
ENDIAN2 BIN EQUATE18 err OPER64 err
EXPANS37 BIN EQUATE4 err PRIV64 err
EXPANS40 BIN EXPR5 err PROC642 err
INOUT BIN INDIR1 err PUSH64 err
INVOKE38 BIN INSTR64 err PUSH642 err
MEMANY BIN INVOK641 err RECORD3 err
MOVDQ16 BIN INVOK642 err SHIFT641 err
MOVDQ32 BIN INVOK643 err SHLD err
RTCOND3 BIN INVOK644 err SIGNIM64 err
STRING2 BIN INVOK645 err SSE464 err
STRING3 BIN INVOK646 err STRUCT29 err
STRING64 BIN INVOK648 err STRUCT37 err
STRUCT02 BIN INVOK649 err STRUCT41 err
VARAR642 BIN INVOK64A err VMX641 err
VARARG64 BIN LARLSL64 err VMX642 err
ALIGN3 err MACRO27 err JWasm exe
ARITH641 err MOV64 err DBGCV obj
AVX1 err MOV642 err LINNUM obj
AVX2 err MOV644 err STRUCT29 obj
AVX3 err MOV645 err
AVX4 err MOVDQ64 err
AVX641 err MOVSP16 err
CALL3 err MOVSPEC err
CALL64 err MOVSPEC2 err
CVTXX64 err MOVSX64 err
JJ, assuming the test is done on a 64-bit OS could you run a test to see if there is any difference between the 32 and 64-bit version?
What is the regression test actually comparing? The instruction encodings at a binary level?
deleted
Hi there,
New version is uploaded on Terfaspace with some bug fixes and speed increase (I hope)
JJ2007, can you please test it for speed now
regards
Quote from: habran on January 22, 2016, 09:57:38 PMJJ2007, can you please test it for speed now
It has become a bit slower, sorry:
HJWasm32 : 6.3 secs->6.8
HJWasm64 : 5.2 secs->5.4
Besides, my testbed throws an exception (with both 32+64 bit versions):
pop edx ; save return address to a global var (allocP saves edx)
call MbAllocP ; reuse two args on stack
push edx ; load return address and fall through to MbAddToHeapTable
MbAddToHeapTable proc
push edx
push ecx
push eax ; the pointer we want to save
sub esp, 2*16
movups [esp], xmm0
movups [esp+16], xmm1
mov edx, offset MbHeapTableGood code:
00405E4B Ú$ 5A pop edx
00405E4C ³. E8 D3EDFFFF call 00404C24
00405E51 ³. 52 push edx
00405E52 ³$ 52 push edx
00405E53 ³. 51 push ecx
00405E54 ³. 50 push eax
00405E55 ³. 83EC 20 sub esp, 20
00405E58 ³. 0F110424 movups [esp], xmm0
00405E5C ³. 0F114C24 10 movups [esp+10], xmm1 ; TestMasmBasic.00405E5C(guessed Arg1,Arg2)
00405E61 ³. BA 30024200 mov edx, offset 00420230Bad code:
00405E3B Ú$ 5A pop edx ; TestMasmBasicHJ32.00405E3B(guessed Arg1,Arg2)
00405E3C ³. E8 D3EDFFFF call 00404C14
00405E41 ³. 52 push edx
00405E42 ³$ 52 push edx ; TestMasmBasicHJ32.00405E42(guessed Arg1,Arg2)
00405E43 ³. 51 push ecx
00405E44 ³. 50 push eax
00405E45 ³. 83EC 20 sub esp, 20
00405E48 ³. 0F110424 movups [esp], xmm0
00405E4C ³. 0F114C24 BA movups [esp-46], xmm1
00405E51 ³. 40 inc eax
00405E52 ³. 0242 00 add al, [edx]
00405E55 ³. 83A2 90010000 and dword ptr [edx+190], 00000000
00405E5C ³. 0F57C0 xorps xmm0, xmm0Hope it helps... :icon14:
deleted
Thanks JJ, I am surprised because I used VS "Favor fast code (/Ot)" option
The error is in OFFSET, which I will check tonight
Can you please test the one from page 2 in this thread and see if there is the same problem
Thanks nidud I will pay attention to those things you pointed out
Quote from: habran on January 23, 2016, 06:18:45 AMCan you please test the one from page 2 in this thread and see if there is the same problem
Page 2 version produces correct code.
Thanks JJ,
That makes it easyer to find the error
Can you post two identical versions, one compiled with the "favour fast code" option, the other one without?
Here they are (fixed bug from before)
One with 'F' i the "fast" one
They both choke, so the /fast option is not the culprit :(
Please explain it in a plain English
That is plain English, my friend :P
They both chokethrow exceptions, so the /fast option is not the culpritresponsible for the problem :(
Now you are talking my language :biggrin:
I figure it out, the new version can not regurgitate OFFSET
I will fix that and than I will post it here
JJ, try now above files, I replaced them with ones that work (fingers crossed ::))
Both work fine :t
(the fast one is marginally slower :icon_mrgreen:)
That is good news, can you show some numbers like timings for building the MasmBasic library
m32lib
asmc.exe
0:20.827s
hwjasm32.exe
0:36.960s
hwjasm.exe 32-bit
0:29.4s
hwjasm.exe 64-bit
0:31.135s
EDIT: corrected tests
I have no errors for the m32 lib build. However, AsmC fails with an exception.
Attached instructions and a batch file.
Thanks JJ :t
I have the same result, that means that this version is stable, so we will release the source probably tonight.
HJWasm will probably run a little bit slower than JWasm because it has to handle double number of instructions and all of them are very complex, so they need a special treatment.
I can not test yet AVX512 instructions, because the processor is not available yet AFAIK but when we get it we will check for errors.
There is no other dissembler available for AVX512 except Agner's Fog OBJCONV
We have cooperated so that both, OBJCONV and HJWasm produce correct output
Cheers!
deleted
deleted
Results for building \Masm32\m32lib:
3901 ms AsmC (today's >64 args version)
4997 ms JWasm
12551 ms HJWasm
16356 ms ML 10.0
16411 ms ML 6.15
Hi,
Thanks to Habran for the excellent work in continuing where JWasm left off.
I have a problem with the latest version of HJWasm.exe (as posted in this thread).
Please could other people confirm whether this is a bug for them or not?
The source code:
.CODE
temp proc
pmullw xmm1, xmm2
temp endp
END
When assembled with hjwasm /win64 x.asm I get the following error
HJWasm v2.13.64bit., Jan 22 2016, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
x.asm(5) : Error A2049: Invalid instruction operands
x.asm: 9 lines, 1 passes, 0 ms, 0 warnings, 1 errors
If pmullw xmm1,xmm2 is changed to vpmullw xmm1,xmm2,xmm3 then the error does not occur.
This module assembles clean with VS2010 ml64.exe V10.00.40219.01. Platform is Windows 7 Ultimate 64-bit SP1
Thanks in advance,
Thanks dawnraider :t
Good find, this was an error which will be fixed in next release
For now here are both binaries with fixed bug
Hi Habran,
Thanks for the fix. This fixes my problem!
Hi Habran,
I have another problem with AVX2 instructions. Here is the code:
.CODE
temp proc
vpblendd xmm1, xmm2, xmm3, 0FFh
temp endp
END
Here is the result:
HJWasm v2.13.64bit., Jan 25 2016, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
x.asm(5) : Error A2209: Syntax error: vpblendd
x.asm: 9 lines, 1 passes, 0 ms, 0 warnings, 1 errors
Please could you check this, and all other AVX2 instructions?
Thanks in advance,
Thanks again dawnraider
That one was not built in, I was not aware of it because I was working on AVX12, now it is
Keep up good work :t
HI Habran,
This is taken from Intel's Software Development Manual. For your reference.
VEX.NDS.128.66.0F3A.W0 02 /r ib
VPBLENDD xmm1, xmm2, xmm3/m128, imm8
VEX.NDS.256.66.0F3A.W0 02 /r ib
VPBLENDD ymm1, ymm2, ymm3/m256, imm8
Thanks.
Thanks dawnraider, but I already updated it in the same place where you took the last one
download it again and try
or you can download it from http://www.terraspace.co.uk/hjwasm.html (http://www.terraspace.co.uk/hjwasm.html)
Hi,
Your last version fixes vpblendd. Thanks!
I found another problem: vpmaskmovd xmm1, xmm2, xmmword ptr [edx]
HJWasm v2.13.64bit., Jan 25 2016, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
x.asm(6) : Error A2209: Syntax error: vpmaskmovd
x.asm: 10 lines, 1 passes, 0 ms, 0 warnings, 1 errors
From the Intel Software Developer's Manual:
VEX.NDS.128.66.0F38.W0 8C /r
VPMASKMOVD xmm1, xmm2, m128
VEX.NDS.256.66.0F38.W0 8C /r
VPMASKMOVD ymm1, ymm2, m256
VEX.NDS.128.66.0F38.W1 8C /r
VPMASKMOVQ xmm1, xmm2, m128
VEX.NDS.256.66.0F38.W1 8C /r
VPMASKMOVQ ymm1, ymm2, m256
VEX.NDS.128.66.0F38.W0 8E /r
VPMASKMOVD m128, xmm1, xmm2
VEX.NDS.256.66.0F38.W0 8E /r
VPMASKMOVD m256, ymm1, ymm2
VEX.NDS.128.66.0F38.W1 8E /r
VPMASKMOVQ m128, xmm1, xmm2
VEX.NDS.256.66.0F38.W1 8E /r
VPMASKMOVQ m256, ymm1, ymm2
Please could you just check that all AVX2 integer instructions are supported?
Thanks in advance.
I have implemented those instructions,
however, I'll check for other missing ones
If you have some I overseen please let me know
Both OK for MB lib, and have become faster :t
HJWasm32 ; 6.3 secs->6.8 ->5.4
HJWasm64 ; 5.2 secs->5.4->4.4
For an easy way to find the new versions , can you put them in one only place ?.
For example here:
http://www.terraspace.co.uk/hjwasm.html
This allow to have a look on it from time to time.
And if can made another required ( very ambitious ?),I wait a 64 bits version with a working debug option.
/Zi .Debugging with source code is really usefull.
Hey,
The new versions will always be kept up-to-date on the Terraspace site (They've just been updated now).
ToutEnMasm, 64bit debugging should work perfectly, I use it all the time in VS2012 and VS2015..
Heres a screen-shot debugging a 64bit app in VS2012:
www.terraspace.co.uk/vs_debug.png (http://www.terraspace.co.uk/vs_debug.png)
I use the command line:
hjwasm64 -c -win64 -Zi -Zd-Zf -Zp8 svo3.asm
Cheers,
John
64bit debugging seems fine with x64dbg as well. I use radasm v2 and have these options set to compile and link:
3,O,$B\HJWASM64.EXE /c -win64 -Zp8 /Zi /win64 /D_WIN64 /Cp /nologo /W2 /Zi /Zd /nologo /I"$I",2
5,O,$B\LINK.EXE /SUBSYSTEM:WINDOWS /DEBUG /DEBUGTYPE:CV /PDB:"$18" /VERSION:4.0 /MACHINE:X64 /LIBPATH:"$L" /OUT:"$5",3,4
I edited my test64.rap file and set file no 18 under [Files] to be 18=Test64.pdb, so that in the linker it uses it /PDB:"$18"
http://postimg.org/image/gt36yuggv/
Thanks jj2007, thanks fearless 8)
Hi Habran,
Thanks for the update! We should create a test function that simply has all the new instructions listed back to back so we test the assembler and the generated code.
We have another problem with instruction encoding. I've also opened a new post here (http://masm32.com/board/index.php?topic=5067.0 (http://masm32.com/board/index.php?topic=5067.0)). Could you please look at this?
00000000 temp proc
00000000 C4E27918CA vbroadcastss xmm1, xmm2
00000005 temp endp
VEX.128.66.0F38.W0 18 /r RM V/V AVX2
VBROADCASTSS xmm1, xmm2
This code appears to work, however:
00000000 temp proc
00000000 62F27D0878CA vpbroadcastb xmm1, xmm2
00000006 temp endp
VEX.128.66.0F38.W0 78 /r RM V/V AVX2
VPBROADCASTB xmm1, xmm2/m8
causes an "illegal instruction" exception. The encoding for vpbroadcastb looks to be one byte too long. Do both of these generated encodings match Intel's specification?
Thanks in advance,
You are doing excellent job dawnraider :t
The problem was that HJWasm produced EVEX code instead of AVX2
I fixed it and uploaded on Teraspace even though the date is 25th it is from today (I don't know yet how to change the date on Teraspace) John will change it when he wakes up
Hi Habran,
Thanks for the update. This release is much better! All instructions now appear to have the correct VEX prefix.
The following AVX2 test code executes fine:
.DATA
ALIGN 16
auArithGreyScale DWORD 000000047h, 0000002DEh, 0000000D6h, 000000000h
.CODE
temp PROC
00000000 C5F877 vzeroall
00000003 C4E27918C9 vbroadcastss xmm1, xmm1
00000008 C4E27978C9 vpbroadcastb xmm1, xmm1
0000000D 488D0500000000 lea rax, auArithGreyScale
00000014 C4E2692C08 vmaskmovps xmm1, xmm2, xmmword ptr [rax]
00000019 C4E2698C08 vpmaskmovd xmm1, xmm2, xmmword ptr [rax]
0000001E C4E36902CBAA vpblendd xmm1, xmm2, xmm3, 0AAh
temp ENDP
Thanks!
:t
Hi,
I've updated both x86 and x64 packages on http://www.terraspace.co.uk/hjwasm.html (http://www.terraspace.co.uk/hjwasm.html)
Cheers!
John
Download the new version 26/01/2016
64 bits Windows 10 compiled OK before update
Quote
listview.asm(64) : Error A2224: Not supported with current output format: frame
listview.asm(65) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(66) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(67) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(102) : Error A2142: Unmatched block nesting: WinMain
listview.asm(104) : Error A2224: Not supported with current output format: frame
listview.asm(105) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(121) : Error A2142: Unmatched block nesting: InsertColumn
listview.asm(123) : Error A2224: Not supported with current output format: frame
listview.asm(124) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(125) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(175) : Error A2142: Unmatched block nesting: ShowFileInfo
listview.asm(177) : Error A2224: Not supported with current output format: frame
listview.asm(178) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(179) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(188) : Error A2159: INVOKE requires prototype for procedure
listview.asm(196) : Error A2142: Unmatched block nesting: FillFileInfo
listview.asm(198) : Error A2224: Not supported with current output format: frame
listview.asm(199) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(225) : Error A2142: Unmatched block nesting: String2Dword
listview.asm(227) : Error A2224: Not supported with current output format: frame
listview.asm(228) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(229) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(230) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(240) : Error A2159: INVOKE requires prototype for procedure
listview.asm(245) : Error A2159: INVOKE requires prototype for procedure
listview.asm(251) : Error A2159: INVOKE requires prototype for procedure
listview.asm(254) : Error A2159: INVOKE requires prototype for procedure
listview.asm(270) : Error A2142: Unmatched block nesting: CompareFunc
listview.asm(272) : Error A2224: Not supported with current output format: frame
listview.asm(273) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(289) : Error A2142: Unmatched block nesting: UpdatelParam
listview.asm(291) : Error A2224: Not supported with current output format: frame
listview.asm(292) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(293) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(305) : Error A2142: Unmatched block nesting: ShowCurrentFocus
listview.asm(309) : Error A2224: Not supported with current output format: frame
listview.asm(310) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(311) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(321) : Error A2159: INVOKE requires prototype for procedure
listview.asm(322) : Error A2159: INVOKE requires prototype for procedure
listview.asm(364) : Error A2159: INVOKE requires prototype for procedure
listview.asm(368) : Error A2159: INVOKE requires prototype for procedure
listview.asm(374) : Error A2159: INVOKE requires prototype for procedure
listview.asm(378) : Error A2159: INVOKE requires prototype for procedure
listview.asm(383) : Error A2159: INVOKE requires prototype for procedure
listview.asm(397) : Error A2142: Unmatched block nesting: WndProc
listview.asm(411) : Error A2159: INVOKE requires prototype for procedure
listview.asm: 414 lines, 1 passes, 469 ms, 0 warnings, 48 errors
Hi,
I'll check with Habran this evening as I know he applied a new change to avoid checking for EVEX encoding when it wasn't required.
This change was applied at about 1pm this afternoon to the latest binaries on the website. Once resolved we will be putting source-code up in github (+wiki and issues pages etc).
So the link will be shared as soon as that's live (and including on the website).
Cheers,
John
QuoteOnce resolved we will be putting source-code up in github (+wiki and issues pages etc).
Where are they?
I posted questions about JWAsm cmdline and never get an answer. I hope, one day perhaps...
Quote from: Grincheux on January 27, 2016, 04:29:32 AM
QuoteOnce resolved we will be putting source-code up in github (+wiki and issues pages etc).
Where are they?
They will be published to github once version 2.13 is stable, there isn't much point before-hand. If this last issue reported (due to today's update ) resolves all remaining issues then I will set it up tomorrow.
The links will be available from the hjwasm website and I'll share them here.
Regards,
John
Quote from: Grincheux on January 27, 2016, 04:30:40 AM
I posted questions about JWAsm cmdline and never get an answer. I hope, one day perhaps...
What was the question? ::)
Binaries and download packages have been updated on the hjwasm site http://www.terraspace.co.uk/hjwasm.html (http://www.terraspace.co.uk/hjwasm.html).
The source code has been hosted on Github at : https://github.com/Terraspace/HJWasm (https://github.com/Terraspace/HJWasm)
Let us know if there are any issues with this latest build (fingers crossed this is now the stable 2.13) and we can continue with new features and improvements.
In the previous version when I did :
Quotejwlink FORMAT WINDOWS PE OPTION NORELOCS,CHECKSUM,ELIMINATE,MAP,NORELOCS,NXCOMPAT,FILLCHAR=42 RESOURCE T01.res FILE T01.obj RUNTIME WINDOWS
It told me that I was creating a QNX file and OPTIONS were not valid.
When I change the command line by :
Quotejwlink FORMAT WINDOWS PE RUNTIME WINDOWS OPTION NORELOCS,CHECKSUM,ELIMINATE,MAP,NORELOCS,NXCOMPAT,FILLCHAR=42 RESOURCE T01.res FILE T01.obj
It is OK.
With this new version I can have any command line it is OK
Quotejwlink FORMAT WINDOWS PE RUNTIME WINDOWS OPTION NORELOCS,CHECKSUM,ELIMINATE,MAP,NORELOCS,NXCOMPAT,FILLCHAR=42 RESOURCE T01.res FILE T01.obj
JWlink Version 1.9beta 13
Portions Copyright (c) 1985-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
loading object files
searching libraries
creating map file
creating a PE executable
Deleted: T01.obj
Deleted: T01.res
Make done.
Thanks Grincheux :t
Congratulation with first release on GitHub :t
I know you may dislike this question ...
Is HJWasm meant to be windows-only assembler ? Does it still contain functionality needed to produce ELF binaries ?
Are bug reports / inquiries on this functionality accepted ?
What do you think about further JWLink development?
Thanks
HJWasm still contains all the existing code from JWasm relating to ELF/OMF and other output formats, so it is technically still supported.
I would consider making required improvements to ELF support (as it is still a modern format in use).
We still need to package up a set of binaries for Linux at some point.
I personally (although this is just my personal opinion) wouldn't look to build any new functionality or binaries for other platforms or output formats as there really isn't any reason for anyone to still be using DOS or OS/2 etc.. (some may disagree).
What might be a nice addition at some point is Mach-O output and OSX binaries, but it's not something I've investigated at all.
I personally have no intention of working on JWLINK as I've never had a need for it.
That being said, I'm more than happy to add the current version + source onto the existing site and github repo's.. (mainly so there is a common source) and others can join in and work on it if they see fit, it is OSS after all :)
One of my questions : http://masm32.com/board/index.php?topic=5063.0
They are in the Campus because I think this place is only reserved for new versions.
Many of my questions are about cmd lines
Sorry Grincheux, I am not familiar with JWLink, I hope someone can answer that question to you from this forum
I did not work on JWLink, but if I ever decide to work on it, I will make it have the same commands as Microsoft linker
Binaries have been updated (dated 27th Jan 2016) on http://www.terraspace.co.uk/hjwasm.html (http://www.terraspace.co.uk/hjwasm.html)
Changes:
1) vextractf128 was encoding the source and destination registers the wrong way around.
2) INCBIN has been heavily optimised, 14mb of incbin data now takes an additional 1-2sec assemble time for me as opposed to 7-8 seconds.
Git repositories are up to date and issues logged.
Regards,
John
Gitter chat room setup at:
https://gitter.im/john-terraspace/HJWASM (https://gitter.im/john-terraspace/HJWASM)
JOHNSA, thank you for quick reply
I don't have GitHub account so I post here first and very important feature request:
#27 System V AMD64 ABI convention (http://sourceforge.net/p/jwasm/feature-requests/27/)
Please, add it as an enhancement .
Without doubt, it's priority number 1 ( talking about Linux functionality)
Next two as discussed in this thread 64bit linux ELF issues (http://sourceforge.net/p/jwasm/discussion/927109/thread/80712144/) are support for shared objects ( arguable ) and for DWARF debugging information format (important) .
I compiled HJWasm with GCC 4.8.4
NOTE: In order to build it for testing purposes function strcmpi was (currently) replaced with strcasecmp in files: hll.c and invoke.c
The output of GCC with lots of warnings (first run , unmodified hll.c and invoke.c) is attached in archive
Please, let me know if I can help you in packaging up a setup of binaries for Linux.
At the moment I'm fighting to death with OWLinux.mak ( which is makefile version for Windows )
BTW , could you , please, explain the meaning of HJWasm's logo string:
QuoteHJWasm v2.13.32bit.
I mean ".32bit" part of it .
P.S.: Please, could you provide a simple example that takes advantages of high level capabilities and features of HJWasm ?
64 bits version on http://www.terraspace.co.uk/hjwasm.html
Quote
----------------------------- option win64 : 11;4;7;3,7,11 ;<<<<<<<<<<< ligne 17, 11=B -----------------------
H:\sdkrc81\shared\sdk64.inc(17) : Error A2235: Constant value too large: Bh
H:\sdkrc81\shared\sdk64.inc(17): Included by
It's an old version,2.12
deleted
Hi,
I've created those issues on the github page and copied across all the details from the sourceforge threads, I'm sure we can do something about some of them at least :)
The logo, at least the .32bit or .64bit part is the build target, so .32bit would be a PE, .64bit a PE+(x64) binary.
I am already putting together an extend set of samples to include into the packages :) great minds!
Help with Linux builds would be fantastic, when I get a chance I will try to get a linux box setup here to use as well.
Quote from: ToutEnMasm on January 28, 2016, 02:46:37 AM
64 bits version on http://www.terraspace.co.uk/hjwasm.html
Quote
----------------------------- option win64 : 11;4;7;3,7,11 ;<<<<<<<<<<< ligne 17, 11=B -----------------------
H:\sdkrc81\shared\sdk64.inc(17) : Error A2235: Constant value too large: Bh
H:\sdkrc81\shared\sdk64.inc(17): Included by
It's an old version,2.12
I've just double checked the package and it's definitely the latest 2.13.64bit ?
Quote from: nidud on January 28, 2016, 02:59:03 AM
A simple makefile for building HJWASM using Open Watcom
SRC = \HJWASM\SRC
INC = $(SRC)\h
OW = \WATCOM
CC = $(OW)\binnt\wcc386 -q -bt=nt -bc -zc -I$(OW)\h;$(OW)\h\nt;$(INC) -3r -obmilrt -s -DNDEBUG
hjwasm.exe:
for %%q in ($(SRC)\*.c) do $(CC) %%q
$(OW)\binnt\wlink N $@ OP q, m System nt file { *.obj }
@del *.obj
This failed, but after a few changes to the source:
- Added proto for Tokenize() in hll.c
- Moved 'comprdsp' in codegen.c to top of function output_opc(C-style)
- Changed 'intptr_t' to 'long' in main.c
- Removed GetResWName() from parser.c(1644)
and lots of warnings from instruct.h:
\HJWASM\SRC\h\instruct.h(165): Warning! W106: Constant out of range - truncated
\HJWASM\SRC\h\instruct.h(187): Warning! W106: Constant out of range - truncated
\HJWASM\SRC\h\instruct.h(188): Warning! W106: Constant out of range - truncated
\HJWASM\SRC\h\instruct.h(745): Warning! W106: Constant out of range - truncated
\HJWASM\SRC\h\instruct.h(745): Warning! W106: Constant out of range - truncated
\HJWASM\SRC\h\instruct.h(745): Warning! W106: Constant out of range - truncated
\HJWASM\SRC\h\instruct.h(745): Warning! W106: Constant out of range - truncated
...
I manage to build a 32-version:
HJWasm v2.13.32bit., Jan 27 2016, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
I fixed math problem and did a speed test:
m32lib:
ClockTicks: 4188 ASMC 2.17
ClockTicks: 4265 ASMC 2.16
ClockTicks: 5547 HJWASM 2.13
ClockTicks: 5563 JWASM 2.12
ClockTicks: 16016 ML-6
ClockTicks: 18265 ML-9
math:
ClockTicks: 6484 ASMC 2.17
ClockTicks: 6813 ASMC 2.16
ClockTicks: 8688 HJWASM 2.13
ClockTicks: 8844 JWASM 2.12
ClockTicks: 10812 ML-9
I then added __JWASM__ to symbols.c
/* table of predefined numeric equates */
static const struct eqitem eqtab[] = {
{ "__HJWASM__", _HJWASM_VERSION_INT_, NULL, NULL },
{ "__JWASM__", 212, NULL, NULL },
and run the regression test: There are now 33 errors.
AVX1 BIN
AVX4 BIN
AVX641 BIN
EXPANS37 BIN
EXPANS40 BIN
INOUT BIN
INVOK644 BIN
INVOK646 BIN
INVOK649 BIN
INVOK64A BIN
MEMANY BIN
MOVDQ16 BIN
MOVDQ32 BIN
MOVDQ64 BIN
RTCOND3 BIN
STRING2 BIN
STRING3 BIN
STRING64 BIN
VARAR642 BIN
VARARG64 BIN
ALIGN3 err
ASMC104 err
AVX2 err
AVX3 err
CALL3 err
DATA7 err
INDIR1 err
MOV645 err
MOVSP16 err
MOVSPEC err
MOVSPEC2 err
PROC641 err
SHLD err
STRUCT29 err
STRUCT37 err
STRUCT41 err
DBGCV obj
STRUCT29 obj
Would you be able to get an x64 build going as well?
I think from the list of changes you've made they seem fairly innocuous, so we should be able to apply them to the code-base in general (applicable to all build targets) ?
main.c //fixed by ToutEnMasm intptr_t instead of long
It appears this was already changed from long to intptr_t ?
It seems to me that GetResWName is still valid in this block and shouldn't be removed? (parser.c 1644)
if ( (GetRegNo( index ) == 4) && (GetResWName( index, NULL ) <= T_RBP )) { /* [E|R]SP? */
The other three changes I've committed to the source as they're harmless:
Added proto for Tokenize() in hll.c (included tokenize.h in hll.c)
Moved 'comprdsp' in codegen.c to top of function output_opc(C-style)
Added { "__JWASM__", 212, NULL, NULL },
@JOHNSA:
Great ! Thank you
That's strange ".32bit" part when executable is x64:
Quote./hjwasm: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=be0168512cdb2cd5bd43581e4db931d6f43547a6, stripped
Logo:
QuoteHJWasm v2.13.32bit., Jan 27 2016, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
usage: HJWasm [ options ] filelist [@env_var]
Run "HJWasm -?" or "HJWasm -h" for more info
x64 Linux binary (GCC 4.8.4) atached
Today I'll try Open Watcom and TCC builds on Linux .
I'm ready to help you with Linux / Linux binaries as much as I can
@NIDUD
Thank you for guidelines
[EDIT]: attachment was removed
The source code in GitHub compiled perfect with VC2015 in 64 bits.
I get just warnings.
But defaut with frame is the same
1>bin.c(229): warning C4146: opérateur moins unaire appliqué à un type non signé, le résultat sera non signé
1>expreval.c(2424): warning C4146: opérateur moins unaire appliqué à un type non signé, le résultat sera non signé
1>expreval.c(2430): warning C4146: opérateur moins unaire appliqué à un type non signé, le résultat sera non signé
1>parser.c(1644): warning C4047: '<=' : les niveaux d'indirection de 'char *' et de 'int' sont différents
1>proc.c(2570): warning C4146: opérateur moins unaire appliqué à un type non signé, le résultat sera non signé
1>proc.c(2716): warning C4146: opérateur moins unaire appliqué à un type non signé, le résultat sera non signé
1>types.c(442): warning C4146: opérateur moins unaire appliqué à un type non signé, le résultat sera non signé
1>types.c(694): warning C4146: opérateur moins unaire appliqué à un type non signé, le résultat sera non signé
1> Génération de code en cours...
1> HJWasm.vcxproj -> H:\HJWasm-master\Win32\Release\HJWasm.exe
========== Génération : 1 a réussi, 0 a échoué, 0 mis à jour, 0 a été ignoré ==========
Quote from: GoneFishing on January 28, 2016, 03:48:59 AM
@JOHNSA:
Great ! Thank you
That's strange ".32bit" part when executable is x64:
Quote./hjwasm: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=be0168512cdb2cd5bd43581e4db931d6f43547a6, stripped
Logo:
QuoteHJWasm v2.13.32bit., Jan 27 2016, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
usage: HJWasm [ options ] filelist [@env_var]
Run "HJWasm -?" or "HJWasm -h" for more info
x64 Linux binary (GCC 4.8.4) atached
Today I'll try Open Watcom and TCC builds on Linux .
I'm ready to help you with Linux / Linux binaries as much as I can
@NIDUD
Thank you for guidelines
I guess for a LINUX build it makes sense due to code in globals.h :)
/* HJWasm version info */
#ifdef _WIN64
#define _HJWASM_VERSION_STR_ "2.13.64bit."
#else
#define _HJWASM_VERSION_STR_ "2.13.32bit."
#endif
Clearly _WIN64 isn't defined, I've tried using __LP32__ and __x86_64__ neither of which work for me under Windows, any suggestions?
I guess you could just define _WIN64 for the Linux X64 build from the make file?
Now it really makes sense, thanks
I'll be quiet for the rest of the day or evening (as it's here)
Don't work too hard :-)
When i was playing round with Jwasm 64 and radasm i used the /D switch to define the _WIN64 like so:
3,O,$B\JWASM64.EXE /c -win64 -Zp8 /Zi /win64 /D_WIN64 /Cp /nologo /W2 /Zi /Zd /nologo /I"$I",2
deleted
There is to jwasm in the http://www.terraspace.co.uk/hjwasm.html
corrected but
Quote
JWASM listview.asm
H:\tut64_partiel\tute31
HJWasm v2.13.64bit., Jan 27 2016, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
listview.asm(64) : Error A2224: Not supported with current output format: frame
listview.asm(65) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(66) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(67) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(102) : Error A2142: Unmatched block nesting: WinMain
listview.asm(104) : Error A2224: Not supported with current output format: frame
listview.asm(105) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(121) : Error A2142: Unmatched block nesting: InsertColumn
listview.asm(123) : Error A2224: Not supported with current output format: frame
listview.asm(124) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(125) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(175) : Error A2142: Unmatched block nesting: ShowFileInfo
listview.asm(177) : Error A2224: Not supported with current output format: frame
listview.asm(178) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(179) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(188) : Error A2159: INVOKE requires prototype for procedure
listview.asm(196) : Error A2142: Unmatched block nesting: FillFileInfo
listview.asm(198) : Error A2224: Not supported with current output format: frame
listview.asm(199) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(225) : Error A2142: Unmatched block nesting: String2Dword
listview.asm(227) : Error A2224: Not supported with current output format: frame
listview.asm(228) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(229) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(230) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(240) : Error A2159: INVOKE requires prototype for procedure
listview.asm(245) : Error A2159: INVOKE requires prototype for procedure
listview.asm(251) : Error A2159: INVOKE requires prototype for procedure
listview.asm(254) : Error A2159: INVOKE requires prototype for procedure
listview.asm(270) : Error A2142: Unmatched block nesting: CompareFunc
listview.asm(272) : Error A2224: Not supported with current output format: frame
listview.asm(273) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(289) : Error A2142: Unmatched block nesting: UpdatelParam
listview.asm(291) : Error A2224: Not supported with current output format: frame
listview.asm(292) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(293) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(305) : Error A2142: Unmatched block nesting: ShowCurrentFocus
listview.asm(309) : Error A2224: Not supported with current output format: frame
listview.asm(310) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(311) : Error A2092: PROC, MACRO or macro loop directive must precede LOCAL
listview.asm(321) : Error A2159: INVOKE requires prototype for procedure
listview.asm(322) : Error A2159: INVOKE requires prototype for procedure
listview.asm(364) : Error A2159: INVOKE requires prototype for procedure
listview.asm(368) : Error A2159: INVOKE requires prototype for procedure
listview.asm(374) : Error A2159: INVOKE requires prototype for procedure
listview.asm(378) : Error A2159: INVOKE requires prototype for procedure
listview.asm(383) : Error A2159: INVOKE requires prototype for procedure
listview.asm(397) : Error A2142: Unmatched block nesting: WndProc
listview.asm(411) : Error A2159: INVOKE requires prototype for procedure
listview.asm: 414 lines, 1 passes, 431 ms, 0 warnings, 48 errors
????????????????????????????????????????????????
@ToutEnMasm, what happens if you specify some flags when compiling?, like so:
JWASM /c -win64 -Zp8 /Zi /win64 /D_WIN64 /Cp /W2 /Zi /Zd listview.asm
deleted
Hi,
Good spotting, didn't see that.
I've updated hll.c to just a prototype without the include and made the other changes in main.c and parser.c
It's all building and testing out fine my side.
Updated source is in the Github repo.
Hopefully we can get some Nix builds! :)
ToutEnMasm, could you post your test source and command line?
So we can narrow down the issue to either a switch or possibly usage of .option etc ?
Thanks!
deleted
Hi nidud, which compiler are you using?
It compiles fine with VS13
It looks to me that your compiler can not handle 'int i'
Tray to declare it before for loop like:
int i;
for ( i = 0; i < len; i++)
CurrSeg->e.seginfo->CodeBuffer[idx++] = *(pBytes++);
I'm afraid I'm too slow and you're applying changes to source code tooo quick ... but finally I got to compile HJWasm as it was in times of post #101 + patched codegen.c (#107 )
Built with Open Watcom C compiler 1.9 , linked with JWLINK on Linux
Size of executable:
Quote337401
Output from file utility:
Quote./hjwasm: ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, not stripped
OW compiler can't produce 64 bit executables.
[EDIT]: Always wanted to ask how to run regression tests from JWASM source code in batch mode ?
deleted
What habran meant is
int i;
for (i = 0; i < len; i++)
instead of
for (int i = 0; i < len; i++)
IIRC MS VS doesn't like it in C mode, but accepts it if the source ending is .cpp.
Quote from: nidud on January 28, 2016, 09:28:20 AM
In C data needs to be declared like { int a,b; /* use a and b */ }, so adding data on the fly generates errors.
This restriction had been removed with ISO/ANSI-C99.
Quote from: nidud on January 28, 2016, 09:28:20 AM
QuoteTray to declare it before for loop like:
Yes, that's a good habit.
In C data needs to be declared like { int a,b; /* use a and b */ }, so adding data on the fly generates errors.
fseek( file, 0L, SEEK_END );
long sz = ftell( file ) - fileoffset;
Ok,
1) I've modified assemble.c (line 253) to declare int i; before the loop.. as this should be more compatible then with non C99 compilers.. github updated.. again.. :)
My test program for 64 bits is here:
http://masm32.com/board/index.php?topic=4528.msg48489#msg48489
He is in tut64_partiel.zip and named tut31nlistview.asm and had a batch for compile.
This time,Iget an assertion failure:
see zip file
istype.cpp line 26
Hi ToutEnMasm,
Your mistake is here:
start:
;fastcall need stack space before call
;one qword for return adress of call
;
add rsp,-(8 + 80 * 8) ; - (align + shadow space) ;generous size + align 16
;invoke DebugBreak
invoke GetModuleHandle, NULL
mov hInstance,rax
mov InitCtrls.dwSize,sizeof INITCOMMONCONTROLSEX
mov InitCtrls.dwICC, ICC_LISTVIEW_CLASSES
invoke InitCommonControlsEx,addr InitCtrls ;cumulatif
invoke WinMain, hInstance,NULL, NULL, SW_SHOWDEFAULT
invoke ExitProcess,eax
end start
You can not do that in x64 code
You have to use 'WinMainCRTStartup PROC FRAME USES ....'
and don't mess with stack alignment HJWasm takes care for you if you use PROC FRAME and :
option casemap : none
option win64 : 11
option frame : auto
option STACKBASE : RSP
There is no mistake here and the proc works perfectly since a long time.
Run the exe.
There is just a stack reserve a little too big.
Don't search here it's a vast of time.
Here the compiled listview with Jwasm 2.13 without your avx 512
Here what see windbg on it,NOTHING:
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred symsrv*symsrv.dll*c:\symbols*c:\windows\symbols*http://msdl.microsoft.com/download/symbols
OK H:\tut64_partiel\tute31
Deferred SRV*C:\WINDOWS\Symbols*http://msdl.microsoft.com/download/symbols
0:000> g
ModLoad: 00007ffc`479c0000 00007ffc`479fb000 C:\WINDOWS\system32\IMM32.DLL
ModLoad: 00007ffc`433c0000 00007ffc`43456000 C:\WINDOWS\system32\uxtheme.dll
ModLoad: 00007ffc`47530000 00007ffc`477ad000 C:\WINDOWS\system32\combase.dll
ModLoad: 00007ffc`44be0000 00007ffc`44c4a000 C:\WINDOWS\system32\bcryptPrimitives.dll
ModLoad: 00007ffc`47a60000 00007ffc`47bba000 C:\WINDOWS\system32\MSCTF.dll
ModLoad: 00007ffc`41490000 00007ffc`414b2000 C:\WINDOWS\system32\dwmapi.dll
ModLoad: 00007ffc`37600000 00007ffc`37874000 C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.10586.0_none_8c15ae12515e1c22\comctl32.DLL
ModLoad: 00007ffc`45680000 00007ffc`45735000 C:\WINDOWS\system32\SHCORE.dll
ModLoad: 00007ffc`44970000 00007ffc`4497f000 C:\WINDOWS\system32\kernel.appcore.dll
ModLoad: 00007ffc`472c0000 00007ffc`47403000 C:\WINDOWS\system32\ole32.dll
ntdll!NtTerminateProcess+0x14:
00007ffc`483e5364 c3 ret
Ok.. I downloaded your source and your full include project..
first thing i had to do was change line 442 of commctrl.sdk
It has a struct member called Frame (which is a reserved word) so I made it _Frame.
Then i created a new batch file to build.. set the includes.. using the latest hjwasm64.exe ... and it works perfectly.. (I still agree with Habran.. you really should never touch RSP.. ever.. and it's best to use WinMainCRTStartup as an actual PROC (rather than just the start: label).
I've attached my folder (including a new build.bat file AND the exe as it's just assembled/linked for me.. which is working fine), using the same hjwasm64 available for download.. and this works perfectly.
The only difference between us might possibly be that I'm using the libs from the platform / windows sdk.. but they should be identical.
Thanks to try
I am a little lost on your various versions of jwasmx64
I get the same result with:
HJWasm v2.13.64bit., Jan 27 2016, Masm-compatible assembler.
Intel(R) Core(TM) i3-4150 CPU @ 3.50GHz
Microsoft Windows 10 Famille Version: 10.0.10586
correct results with 32 bits asm compile
On the RSP use,see:
http://blogs.msdn.com/b/ntdebugging/archive/2009/01/09/challenges-of-debugging-optimized-x64-code.aspx
It's the better and usable information on the subject
HJWasm will automatically allocate and utilise the stack space (following the abi).
1) so a minimum of 32 bytes are always reserved
2) if you have 4+ args and shadow space enabled, the args will be copied
3) if you don't have shadow space enabled (which you always should by virtue of win64:11).. then no home space are used
4) irrespective of 2 and 3.. if there are unused slots in the homespace these will be used for non-volatiles (preserved via USES) AND / OR locals..
5) each proc will automatically determine the maximum shadow space requirement of all invokes within itself and adjust accordingly at prologue
So.. it's basically exactly what a C++ compiler would do with optimisations on.. except perhaps for using RSP for all references instead of RBP.
So.. based on that
1) NEVER use push/pop at all ever for anything..
2) NEVER touch RSP..
3) 1+2 will make your life much happier and trouble-free :)
I know all that and use the normal crt winmain in my other sources
The version of Jwasm64 who offer no problem for me is this one:
http://masm32.com/board/index.php?topic=4256.msg45376#msg45376
No problem of Frame.
Perhaps made you your compile in an another system than Windows 10 ?
Thanks Johnsa :t
Quote from: johnsa on January 28, 2016, 09:42:26 PM
HJWasm will automatically allocate and utilise the stack space (following the abi).
1) so a minimum of 32 bytes are always reserved
2) if you have 4+ args and shadow space enabled, the args will be copied
3) if you don't have shadow space enabled (which you always should by virtue of win64:11).. then no home space are used
4) irrespective of 2 and 3.. if there are unused slots in the homespace these will be used for non-volatiles (preserved via USES) AND / OR locals..
5) each proc will automatically determine the maximum shadow space requirement of all invokes within itself and adjust accordingly at prologue
So.. it's basically exactly what a C++ compiler would do with optimisations on.. except perhaps for using RSP for all references instead of RBP.
So.. based on that
1) NEVER use push/pop at all ever for anything..
2) NEVER touch RSP..
3) 1+2 will make your life much happier and trouble-free :)
Hey people, keep these things on your mind when you try to do something
EXTRAORDINARY ::)
JOHNSA,
GCC 4.8.4 build SUCCESSFUL, log attached
CHAHGES: strcmpi -> strcasecmp in hll.c and invoke.c
Note, that resulting 64 bit executable still reports :
QuoteHJWasm v2.13.32bit
Maybe add #ifdef __UNIX__ case to globals.h ?
Today I'll try to write OWLinux.mak for Linux . Original OWLinux.mak is supposed to generate Linux binary from Windows
( cross-compilation) .
Quote from: johnsa on January 28, 2016, 11:10:22 AM
...
Ok,
1) I've modified assemble.c (line 253) to declare int i; before the loop.. as this should be more compatible then with non C99 compilers.. github updated.. again.. :)
Open Watcom 1.9 doesn't like chages you have made :
Quote
assemble.c(253): Error! E1077: Missing '}'
assemble.c(253): Error! E1077: Missing '}'
assemble.c(254): Error! E1099: Statement must be inside function. Probable cause: missing {
assemble.c(260): Error! E1099: Statement must be inside function. Probable cause: missing {
make: *** [OWLinuxR/assemble.o] Error 4
Initial version ( post #101, before changes) was OK
Quote from: GoneFishing on January 29, 2016, 12:45:10 AM
Quote from: johnsa on January 28, 2016, 11:10:22 AM
...
Ok,
1) I've modified assemble.c (line 253) to declare int i; before the loop.. as this should be more compatible then with non C99 compilers.. github updated.. again.. :)
Open Watcom 1.9 doesn't like chages you have made :
Quote
assemble.c(253): Error! E1077: Missing '}'
assemble.c(253): Error! E1077: Missing '}'
assemble.c(254): Error! E1099: Statement must be inside function. Probable cause: missing {
assemble.c(260): Error! E1099: Statement must be inside function. Probable cause: missing {
make: *** [OWLinuxR/assemble.o] Error 4
Initial version ( post #101, before changes) was OK
The only thing I can think is to replace it with:
int i;
for (i = 0; i < len; i++)
{
CurrSeg->e.seginfo->CodeBuffer[idx++] = *(pBytes++);
}
Perhaps the compiler doesn't understand single line for's without the { }'s.. this is done and committed to git.
Quote from: GoneFishing on January 29, 2016, 12:07:25 AM
JOHNSA,
GCC 4.8.4 build SUCCESSFUL, log attached
CHAHGES: strcmpi -> strcasecmp in hll.c and invoke.c
Note, that resulting 64 bit executable still reports :
QuoteHJWasm v2.13.32bit
Maybe add #ifdef __UNIX__ case to globals.h ?
Today I'll try to write OWLinux.mak for Linux . Original OWLinux.mak is supposed to generate Linux binary from Windows
( cross-compilation) .
Excellent!
Once we have an x86/x64 build I'll put them up on the site too and add the mak file to the repository.
The problem with __UNIX__ is it still won't determine if the compilation target is 32bit or 64bit...
Habran, how do you feel about just removing that from the console output? :)
Quote from: johnsa on January 29, 2016, 03:04:11 AM
...
The only thing I can think is to replace it with:
int i;
for (i = 0; i < len; i++)
{
CurrSeg->e.seginfo->CodeBuffer[idx++] = *(pBytes++);
}
Perhaps the compiler doesn't understand single line for's without the { }'s.. this is done and committed to git.
Nope , still shows errors:
assemble.c(253): Error! E1077: Missing '}'
assemble.c(253): Error! E1077: Missing '}'
assemble.c(254): Error! E1099: Statement must be inside function. Probable cause: missing {
assemble.c(261): Error! E1099: Statement must be inside function. Probable cause: missing {
Error(E42): Last command making (OWLinuxR/assemble.obj) returned a bad status
Error(E02): Make execution terminated
OW wants and likes this :
//int i;
for (; len; len--)
CurrSeg->e.seginfo->CodeBuffer[idx++] = *(pBytes++);Is it the same ? I noticed this notation in FillDataBytes routine
Now it stops here:
directiv.c(264): Error! E1077: Missing '}'
directiv.c(264): Error! E1077: Missing '}'
directiv.c(264): Warning! W107: Missing return value for function 'IncBinDirective'
directiv.c(264): Error! E1011: Symbol 'file' has not been declared
directiv.c(264): Warning! W102: Type mismatch (warning)
directiv.c(264): Note! I2003: source conversion type is 'int '
directiv.c(264): Note! I2004: target conversion type is 'struct __iobuf *'
directiv.c(264): Note! I2002: 'ftell' defined in: /home/snark/Projects/OW19/binl/lh/stdio.h(290)
directiv.c(264): Error! E1011: Symbol 'fileoffset' has not been declared
directiv.c(264): Error! E1054: Expression must be constant
directiv.c(265): Error! E1009: Expecting ')' but found '0L'
directiv.c(265): Error! E1026: Invalid declarator
directiv.c(265): Error! E1009: Expecting ',' but found '0L'
directiv.c(265): Error! E1026: Invalid declarator
directiv.c(265): Error! E1026: Invalid declarator
directiv.c(265): Error! E1009: Expecting ',' but found '0'
directiv.c(265): Error! E1026: Invalid declarator
directiv.c(265): Error! E1009: Expecting ',' but found ')'
directiv.c(265): Error! E1026: Invalid declarator
directiv.c(266): Error! E1024: Declared symbol 'pBinData' is not in parameter list
directiv.c(266): Error! E1009: Expecting ',' but found '='
directiv.c(266): Error! E1009: Expecting ')' but found 'unsigned'
directiv.c(266): Error! E1026: Invalid declarator
directiv.c(266): Error! E1009: Expecting ',' but found 'char'
directiv.c(266): Error! E1026: Invalid declarator
directiv.c(266): Error! E1147: Too many errors: compilation aborted
Error(E42): Last command making (OWLinuxR/directiv.obj) returned a bad status
Error(E02): Make execution terminated
Wooo... nothing has been changed there at all so it's not something I've done :)
Sounds like there is something wrong with OW (or it's options),
//int i;
for (; len; len--)
CurrSeg->e.seginfo->CodeBuffer[idx++] = *(pBytes++);
that really shouldn't be necessary even in older C syntax.. they're semantically totally different (one is modifying the passed in parameter, the other is using a newly declared loop variable)... and all C supports an "init condition" section of the for loop..?!?
Well , so it's two different things
Files directive.c in your initial commit and as it is now differ . You may compare them . If it's not you who changed the code - then who else?
Anyways, tell me which compilers do you want to keep satisfied on Linux
P.S.: I use original Japheth's makefile with my paths and it works fine with your initial code + modified codegen.c
In ANSI C / C89 definitions must be done at begin of functions - mixing statements and definitions is not allowed.
For Open Watcom 1.9, you can activate C99 support (https://en.wikipedia.org/wiki/Watcom_C/C%2B%2B_compiler#C99) due to cmd-line option -za99.
QWORD, you're a magician :t
I've added this option to original makefile and it worked fine !
Ok,
Can we then agree for any compiler / build-target it should support C99 and that option should be used to build the solution.. I think that's reasonable?
Or does anyone feel we should stick to full ANSI C compliance?
Ok.
Valuable post : http://masm32.com/board/index.php?topic=1977.msg21753#msg21753
I didn't have luck with TCC today (errors at link stage), it turned out that it can't handle redefs
Ok... I decided to stick to ANSI C for now, I've modified all those functions to be ANSI C compliant and made the same changes to invoke.c and hll.c
(strcasecmp).. using #defines in globals.h to make that Windows compatible.
All work from my side in Visual C++
Github updated, GoneFishing do you want to try grab the full source / latest commit and make sure that works with OW / GCC and your make files?
Cheers
Sure :t
already going to GitHub
GCC build successful
No .32bit part , doesn't require any editing
See atached log for warnings
OW build successful ( linked with JWlink Version 1.9beta 13)
no -za99 switch needed
log attached, error at the end of file is false one because output executable has "." at the end (no extension) - Japheth's style :t
[EDIT]: all makefiles are original ones . GccUnix.mak - no modifications needed, OWLinux.mak ( should be passed to WMAKE ) - paths must be set to OW toolchain, "\" replaced by "/" .
:biggrin:
The last version on github is OK for me (WINDOWS 10) ,no more FRAME problem
An update per day ok, every five minutes I can't
Quote from: Grincheux on January 29, 2016, 05:59:42 AM
An update per day ok, every five minutes I can't
Hey.. don't blame us for being proactive :) Only download it once a day then ;) 8)
Quote from: ToutEnMasm on January 29, 2016, 05:13:10 AM
:biggrin:
The last version on github is OK for me (WINDOWS 10) ,no more FRAME problem
Excellente :)
I'll build new packages and update the site.
Thanks all for the assistance!
Now to try hunt down this ever so frustrating AVX (vex encoded) breakpoint issue...
QuoteHey.. don't blame us for being proactive :) Only download it once a day then
That's what I do
I never had answer about JWAsm switch :
-Fd which does not work like said in the help file
-zlc -zld -zlf -zlp -zls : ?
-zzs
It would be great if someone posted simple example with AVX512 instructions .
I want to compile and disasm it .
Hi GoneFishing,
Here is an example with most AVX51F instructions
Habran beat me to it :)
PS.. I've now setup a TravisCI job linked to github.. using the mak files it's (succesfully..yay) building the linux x64 packages using gcc and clang.. badge visible on the readme.md ..
Thank you, HABRAN
JOHNSA, I've already noticed it on GItHub :t
HI Grincheux,
It is not any more JWasm, it is now HJWasm
Good question is already half an answer ;)
What was your question about, what switches you want to use and for which purpose?
Hi Johnsa, there is no need to ask me for agreement, I trust you totally 8)
HABRAN , I've done it !
I must say , that was really good SIMPLE example :biggrin:
I had to comment out FRAME in main proc
Disasm attached
[EDIT]: Here's HJWasm's latest builds output:
GCC 4.8.4 64 bit:
Quotesimple.asm: 9442 lines, 3 passes, 55063 ms, 0 warnings, 0 errors
OW 1.9 32 bit:
Quotesimple.asm: 9442 lines, 3 passes, 7 ms, 0 warnings, 0 errors
Impressive !
[EDIT]: Interestingly that OW build sometimes reports only 2 passes and 5 ms . Timings differ too much . Could it be an error?
NOTE that OW build is statically linked .
[EDIT]: added greped errors to attaches
7ms seems a bit optimistic anyway, 55 seconds seems a bit (a lot actually) on the slow side too ..
For me that file takes 49ms / 2 passes always..
Win7, x64, hjwasm64.exe ... VS2015 build.
Machine wise, core i7 dell laptop..
checked it with time utility :
Quotetime ./hjwasm. -q -elf64 simple.asm
real 0m0.052s
user 0m0.049s
sys 0m0.003s
Celeron Dual Core 2.6
What do 'real', 'user' and 'sys' mean in the output of time(1)? (http://stackoverflow.com/questions/556405/what-do-real-user-and-sys-mean-in-the-output-of-time1)
If you want to have a proper disassembly use Agner's OBJCONV, it produces a perfect output which you can use again to build the same binaries from it
Yes, I know about it.
I wanted to test it in SDE - Intel® Software Development Emulator
include \masm32\include\masm32rt.inc
opax macro arg
Local oa, tmp$
oa = opattr arg
tmp$ CATSTR <TheArg=>, <arg>, < with opattr=>, %oa
% echo tmp$
ENDM
.code
start:
opax DWORD PTR [ebx]
opax -DWORD PTR [ebx] ; <<<< assembles fine with MASM
print "ok"
exit
end start
You are correct JJ, however, this is JWasm fault
I will see why is it happening and try to fix it in HJWasm,
however, you are aware that at this time in the year I am busy with the Australian Open 8)
You can call the assembler HJWasm, Toto... it will stay JWAsm for me.
When it was named JWAsm I did not have any answer I see that now it is the same. You make pleasure to your self in writing such a program, you ask us for tests but that's all.
QuoteHI Grincheux,
It is not any more JWasm, it is now HJWasm
Good question is already half an answer ;)
What was your question about, what switches you want to use and for which purpose?
********* Test of avx,simple.asm win10 ************
Various crash without change of the hjwasm options
Quote
.686P
; .XMM
; .MMX
;
.x64 ; -pe requires to set cpu, model & language
.model flat, fastcall
option casemap : none
option win64 : 11
option frame : auto
option STACKBASE : RSP
codegen.c line 1274 runtime check failure
if (!comprdsp) CodeInfo->tuple = 0; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Quote from: jj2007 on January 29, 2016, 09:27:08 AM
include \masm32\include\masm32rt.inc
opax macro arg
Local oa, tmp$
oa = opattr arg
tmp$ CATSTR <TheArg=>, <arg>, < with opattr=>, %oa
% echo tmp$
ENDM
.code
start:
opax DWORD PTR [ebx]
opax -DWORD PTR [ebx] ; <<<< assembles fine with MASM
print "ok"
exit
end start
I've logged this as an issue on github, I'll leave it to Habran to investigate this one :)
Quote from: ToutEnMasm on January 29, 2016, 05:36:14 PM
********* Test of avx,simple.asm win10 ************
Various crash without change of the hjwasm options
Quote
.686P
; .XMM
; .MMX
;
.x64 ; -pe requires to set cpu, model & language
.model flat, fastcall
option casemap : none
option win64 : 11
option frame : auto
option STACKBASE : RSP
codegen.c line 1274 runtime check failure
if (!comprdsp) CodeInfo->tuple = 0; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Are you getting the runtime check failure when assembling a file?
Could you post source of the test file so we can check it?
Thanks,
Quote from: Grincheux on January 29, 2016, 07:58:31 AM
QuoteHey.. don't blame us for being proactive :) Only download it once a day then
That's what I do
I never had answer about JWAsm switch :
-Fd which does not work like said in the help file
-zlc -zld -zlf -zlp -zls : ?
-zzs
1) zzs is well explained (only applies when using Wlink and if the module has a fixed starting address.. so this wouldn't be relevant in any normal scenario).
Option -zlc:
suppresses writing OMF coment records about data in Code segments. These records may help a disassembler to produce nicer listings.
Option -zld:
suppresses writing an OMF coment record for each Code segment telling the linker that far calls to targets in the same segments should be optimized. This is more or less a feature for 16-bit code only.
Both of these only apply to OMF format output.. and zld only really for 16bit code.. once again this is all really legacy stuff.
Options -zlf, -zlp and -zls do reduce size of the COFF output module. They might be useful if lots of - small - modules are to be assembled and put into a static library.
-zlf suppresses the @file entry in the COFF symbol table. This entry is usually used for debugging purposes only and hence a - pretty small - amount of space can be saved.
-zlp suppresses static (=private) procedures to be included into the COFF symbol table - as long as they aren't referenced absolutely. Such procedures aren't needed for the linking process. However, since the linker has no knowledge of them then, they will also disappear from the linker-generated map-file.
-zls suppresses the auxiliary entries for sections in the COFF symbol table. These entries may not be needed in all cases and thus a little space is saved.
Once again.. I can't see any of these being relevant, -zls possibly.. but who needs to save a few bytes in the obj file ??
-Fd (only applies to jwlink and wlink).. it basically allows you to link the final executable without requiring the lib files.. once again.. why would you need it? Unless you had a dll without the lib file in the first place, but then you could just use loadlibrary..
Hopefully this helps a bit, basically.. they're all obsolete (to me anyway) :)
GCC debug build
Test of Debug option :
-dr Display reserved words
simple.asm:
----------------------------------------------------------------
VPMASKMOVD xmm1, xmm2,m128
simple.asm(89) : Error A2049: Invalid instruction operands
VPMASKMOVQ xmm1, xmm2,m128
simple.asm(90) : Error A2049: Invalid instruction operands
VPMASKMOVD m128, xmm1,xmm2
simple.asm(91) : Error A2049: Invalid instruction operands
VPMASKMOVQ m128, xmm2,xmm2
simple.asm(92) : Error A2049: Invalid instruction operands
VPMASKMOVD ymm1, ymm2,m256
simple.asm(93) : Error A2049: Invalid instruction operands
VPMASKMOVQ ymm1, ymm2,m256
simple.asm(94) : Error A2049: Invalid instruction operands
VPMASKMOVD [rcx], ymm1,ymm2
simple.asm(95) : Error A2049: Invalid instruction operands
VPMASKMOVQ m256, ymm1,ymm2
simple.asm(96) : Error A2049: Invalid instruction operands
VMOVHPD xmm2, xmm1, [rcx]
simple.asm(103) : Error A2049: Invalid instruction operands
VMOVHPD xmm21, xmm1, [rcx]
simple.asm(105) : Error A2049: Invalid instruction operands
VMOVLPD xmm2, xmm1, [rcx]
simple.asm(108) : Error A2049: Invalid instruction operands
VMOVLPD xmm21, xmm1, [rcx]
simple.asm(110) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,zmm6
simple.asm(190) : Error A2049: Invalid instruction operands
vptestnmd k5{k7},zmm15,zmm6
simple.asm(191) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,ZMMWORD PTR [rcx]
simple.asm(192) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,ZMMWORD PTR [rax+r14*8+123h]
simple.asm(193) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,DWORD PTR [rcx]{1to16}
simple.asm(194) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,ZMMWORD PTR [rdx+1fc0h]
simple.asm(195) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,ZMMWORD PTR [rdx+200h]
simple.asm(196) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,ZMMWORD PTR [rdx-200h]
simple.asm(197) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,ZMMWORD PTR [rdx-2040h]
simple.asm(198) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,DWORD PTR [rdx+1fch]{1to16}
simple.asm(199) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,DWORD PTR [rdx+200h]{1to16}
simple.asm(200) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,DWORD PTR [rdx-200h]{1to16}
simple.asm(201) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,DWORD PTR [rdx-204h]{1to16}
simple.asm(202) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,zmm6
simple.asm(203) : Error A2049: Invalid instruction operands
vptestnmq k5{k7},zmm15,zmm6
simple.asm(204) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,ZMMWORD PTR [rcx]
simple.asm(205) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,ZMMWORD PTR [rax+r14*8+123h]
simple.asm(206) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,QWORD PTR [rcx]{1to8}
simple.asm(207) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,ZMMWORD PTR [rdx+1fc0h]
simple.asm(208) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,ZMMWORD PTR [rdx+200h]
simple.asm(209) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,ZMMWORD PTR [rdx-200h]
simple.asm(210) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,ZMMWORD PTR [rdx-2040h]
simple.asm(211) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,QWORD PTR [rdx+3f8h]{1to8}
simple.asm(212) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,QWORD PTR [rdx+400h]{1to8}
simple.asm(213) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,QWORD PTR [rdx-400h]{1to8}
simple.asm(214) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,QWORD PTR [rdx-408h]{1to8}
simple.asm(215) : Error A2049: Invalid instruction operands
VPMULLQ xmm1 {k1}{z}, xmm2,xmm3
simple.asm(217) : Error A2049: Invalid instruction operands
VPMADD52HUQ xmm1 {k1}{z},xmm2,xmm3
simple.asm(276) : Error A2049: Invalid instruction operands
VPMADD52HUQ xmm1 {k1}{z},xmm2,[rcx]
simple.asm(277) : Error A2049: Invalid instruction operands
VPMADD52HUQ ymm1 {k1}{z},ymm2,ymm3
simple.asm(278) : Error A2049: Invalid instruction operands
VPMADD52HUQ ymm1 {k1}{z},ymm2,[rcx]
simple.asm(279) : Error A2049: Invalid instruction operands
VPMADD52HUQ zmm1 {k1}{z},zmm2,zmm3
simple.asm(280) : Error A2049: Invalid instruction operands
VPMADD52HUQ zmm1 {k1}{z},zmm2,[rcx]
simple.asm(281) : Error A2049: Invalid instruction operands
VPMADD52LUQ xmm1 {k1}{z},xmm2,xmm3
simple.asm(283) : Error A2049: Invalid instruction operands
VPMADD52LUQ xmm1 {k1}{z},xmm2,[rcx]
simple.asm(284) : Error A2049: Invalid instruction operands
VPMADD52LUQ ymm1 {k1}{z},ymm2,ymm3
simple.asm(285) : Error A2049: Invalid instruction operands
VPMADD52LUQ ymm1 {k1}{z},ymm2,[rcx]
simple.asm(286) : Error A2049: Invalid instruction operands
VPMADD52LUQ zmm1 {k1}{z},zmm2,zmm3
simple.asm(287) : Error A2049: Invalid instruction operands
VPMADD52LUQ zmm1 {k1}{z},zmm2,[rcx]
simple.asm(288) : Error A2049: Invalid instruction operands
simple.asm(288) : Fatal error A1113: Too many errors
Assembling (with debug build) without -dr switch gives the same errors
It looks like GCC doesn't build properly
I tried to build with Code:Blocks and didn't work properly
VS doesn't have any problems to build binaries and exe is running flawlessly
I just tested it one hour ago with the newest sources from GIt
Quote from: GoneFishing on January 29, 2016, 09:08:24 PM
GCC debug build
Test of Debug option :
-dr Display reserved words
simple.asm:
----------------------------------------------------------------
VPMASKMOVD xmm1, xmm2,m128
simple.asm(89) : Error A2049: Invalid instruction operands
VPMASKMOVQ xmm1, xmm2,m128
simple.asm(90) : Error A2049: Invalid instruction operands
VPMASKMOVD m128, xmm1,xmm2
simple.asm(91) : Error A2049: Invalid instruction operands
VPMASKMOVQ m128, xmm2,xmm2
simple.asm(92) : Error A2049: Invalid instruction operands
VPMASKMOVD ymm1, ymm2,m256
simple.asm(93) : Error A2049: Invalid instruction operands
VPMASKMOVQ ymm1, ymm2,m256
simple.asm(94) : Error A2049: Invalid instruction operands
VPMASKMOVD [rcx], ymm1,ymm2
simple.asm(95) : Error A2049: Invalid instruction operands
VPMASKMOVQ m256, ymm1,ymm2
simple.asm(96) : Error A2049: Invalid instruction operands
VMOVHPD xmm2, xmm1, [rcx]
simple.asm(103) : Error A2049: Invalid instruction operands
VMOVHPD xmm21, xmm1, [rcx]
simple.asm(105) : Error A2049: Invalid instruction operands
VMOVLPD xmm2, xmm1, [rcx]
simple.asm(108) : Error A2049: Invalid instruction operands
VMOVLPD xmm21, xmm1, [rcx]
simple.asm(110) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,zmm6
simple.asm(190) : Error A2049: Invalid instruction operands
vptestnmd k5{k7},zmm15,zmm6
simple.asm(191) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,ZMMWORD PTR [rcx]
simple.asm(192) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,ZMMWORD PTR [rax+r14*8+123h]
simple.asm(193) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,DWORD PTR [rcx]{1to16}
simple.asm(194) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,ZMMWORD PTR [rdx+1fc0h]
simple.asm(195) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,ZMMWORD PTR [rdx+200h]
simple.asm(196) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,ZMMWORD PTR [rdx-200h]
simple.asm(197) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,ZMMWORD PTR [rdx-2040h]
simple.asm(198) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,DWORD PTR [rdx+1fch]{1to16}
simple.asm(199) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,DWORD PTR [rdx+200h]{1to16}
simple.asm(200) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,DWORD PTR [rdx-200h]{1to16}
simple.asm(201) : Error A2049: Invalid instruction operands
vptestnmd k5,zmm15,DWORD PTR [rdx-204h]{1to16}
simple.asm(202) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,zmm6
simple.asm(203) : Error A2049: Invalid instruction operands
vptestnmq k5{k7},zmm15,zmm6
simple.asm(204) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,ZMMWORD PTR [rcx]
simple.asm(205) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,ZMMWORD PTR [rax+r14*8+123h]
simple.asm(206) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,QWORD PTR [rcx]{1to8}
simple.asm(207) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,ZMMWORD PTR [rdx+1fc0h]
simple.asm(208) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,ZMMWORD PTR [rdx+200h]
simple.asm(209) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,ZMMWORD PTR [rdx-200h]
simple.asm(210) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,ZMMWORD PTR [rdx-2040h]
simple.asm(211) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,QWORD PTR [rdx+3f8h]{1to8}
simple.asm(212) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,QWORD PTR [rdx+400h]{1to8}
simple.asm(213) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,QWORD PTR [rdx-400h]{1to8}
simple.asm(214) : Error A2049: Invalid instruction operands
vptestnmq k5,zmm15,QWORD PTR [rdx-408h]{1to8}
simple.asm(215) : Error A2049: Invalid instruction operands
VPMULLQ xmm1 {k1}{z}, xmm2,xmm3
simple.asm(217) : Error A2049: Invalid instruction operands
VPMADD52HUQ xmm1 {k1}{z},xmm2,xmm3
simple.asm(276) : Error A2049: Invalid instruction operands
VPMADD52HUQ xmm1 {k1}{z},xmm2,[rcx]
simple.asm(277) : Error A2049: Invalid instruction operands
VPMADD52HUQ ymm1 {k1}{z},ymm2,ymm3
simple.asm(278) : Error A2049: Invalid instruction operands
VPMADD52HUQ ymm1 {k1}{z},ymm2,[rcx]
simple.asm(279) : Error A2049: Invalid instruction operands
VPMADD52HUQ zmm1 {k1}{z},zmm2,zmm3
simple.asm(280) : Error A2049: Invalid instruction operands
VPMADD52HUQ zmm1 {k1}{z},zmm2,[rcx]
simple.asm(281) : Error A2049: Invalid instruction operands
VPMADD52LUQ xmm1 {k1}{z},xmm2,xmm3
simple.asm(283) : Error A2049: Invalid instruction operands
VPMADD52LUQ xmm1 {k1}{z},xmm2,[rcx]
simple.asm(284) : Error A2049: Invalid instruction operands
VPMADD52LUQ ymm1 {k1}{z},ymm2,ymm3
simple.asm(285) : Error A2049: Invalid instruction operands
VPMADD52LUQ ymm1 {k1}{z},ymm2,[rcx]
simple.asm(286) : Error A2049: Invalid instruction operands
VPMADD52LUQ zmm1 {k1}{z},zmm2,zmm3
simple.asm(287) : Error A2049: Invalid instruction operands
VPMADD52LUQ zmm1 {k1}{z},zmm2,[rcx]
simple.asm(288) : Error A2049: Invalid instruction operands
simple.asm(288) : Fatal error A1113: Too many errors
Assembling (with debug build) without -dr switch gives the same errors
Out of interest .. did you add -win64 and -Zp8 as a switch when assembling? (I think... it might only work with that flag set)
Quote from: habran on January 29, 2016, 09:30:40 PM
It looks like GCC doesn't build properly
I tried to build with Code:Blocks and didn't work properly
VS doesn't have any problems to build binaries and exe is running flawlessly
I just tested it one hour ago with the newest sources from GIt
Did you try to assemble simple.asm with DEBUG BUILD of HJWasm?
[EDIT] You're right , something is wrong with debug GCC build . Debug OW build assembles simple.asm just fine.
Quote from: johnsa on January 29, 2016, 09:35:00 PM
...
Out of interest .. did you add -win64 and -Zp8 as a switch when assembling? (I think... it might only work with that flag set)
No, I didn't use those switches . Tried them now - errors remain the same . Of course it's up to you to decide is it an interesting error or not .
Glad that you confirmed that :t
We appreciate you cooperation and your efforts mate 8)
I wonder what the gcc debug build could be doing, which gcc version is it again?
Quote from: johnsa on January 29, 2016, 10:03:14 PM
I wonder what the gcc debug build could be doing, which gcc version is it again?
JOHNSA, GCC 4.8.4
I ran GCC debug build with trace switch , all debug output is in attachment .
Quote from: habran on January 29, 2016, 10:01:13 PM
Glad that you confirmed that :t
We appreciate you cooperation and your efforts mate 8)
Thanks, HABRAN .
I'm glad to be a little bit helpful.
You are doing a great job GoneFishing :bgrin:
jj2007,
opax -DWORD PTR[rbx]; << << assembles fine with MASM
It shouldn't because it is wrong
JWasm see that '-' as error because it does better job than MASM
If you were an assembler and come to such a statement wouldn't you complain ;)
I know for sure that you would screem :biggrin:
Quote
Are you getting the runtime check failure when assembling a file?
Could you post source of the test file so we can check it?
Thanks,
That's clear in the post,it's the compiled test of simple.asm posted by habran.
He miss some options.
http://masm32.com/board/index.php?topic=5035.msg54623#msg54623
Ok,
I have GCC chain + mingw x64 building HJWasm on Windows.
I get the same warnings as mentioned.
I believe the issue with the build (and why it won't assemble) are those warnings about truncation happening to the instruction definitions:
H/instruct.h:1846:120: warning: large integer implicitly truncated to unsigned t
ype [-Woverflow]
insn(VPMASKMOVD,1, OpCls( XMM_M128, XMM, NONE ), F_660F38,0, n
o_WDS, 0x8C, 0x00, P_686|P_AVX, DSIZE ) //AVX2
^
DSIZE is an enum member, value = 0x40 .. so it's definitely not overflowing.. some more non C99 issues I believe...
With Pellesc x64 broken exe.\H\instruct.h(165): warning #2110: Initializer exceeds bit-field width.
insn(CMPSD, 2, OpCls( XMM, XMM_M64, I8_U ), F_F20F, 1, no_WDS, 0xC2, 0x00, P_686|P_SSE2,W1|QSIZE|T1S)
.\H\instruct.h(187): warning #2110: Initializer exceeds bit-field width.
insn(MOVSD, 2, OpCls( XMM, XMM_M64, NONE ), F_F20F, 1, no_WDS, 0x10, 0x00, P_686|P_SSE2,W1|QSIZE|T1S)
.\H\instruct.h(188): warning #2110: Initializer exceeds bit-field width.
insn(MOVSD, 3, OpCls( M64, XMM, NONE ), F_F20F, 0, no_WDS, 0x11, 0x00, P_686|P_SSE2,W1|QSIZE|T1S)
.\H\instruct.h(745): warning #2110: Initializer exceeds bit-field width.
arfl( ADD, add, 0x58 )
arfl( DIV, div, 0x5E )
arfl( MAX, max, 0x5F )
arfl( MIN, min, 0x5D )
arfl( MUL, mul, 0x59 )
arfl( SQRT, sqrt, 0x51 )
arfl( SUB, sub, 0x5C )
...HJWasm v2.13, Jan 29 2016, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
simple.asm(1203) : Error A2168: General Failure
*** Process returned 1 ***
Press any key to continue...
With MSVC14 cl + link and WDDK libs\HJWasm\MSVC14>hjwasm -win64 ..\..\simple.asm
HJWasm v2.13, Jan 29 2016, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
..\..\simple.asm: 9442 lines, 2 passes, 150 ms, 0 warnings, 0 errors
\HJWasm\MSVC14>hjwasm64 -win64 ..\..\simple.asm
HJWasm v2.13, Jan 29 2016, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
..\..\simple.asm: 9442 lines, 3 passes, 114 ms, 0 warnings, 0 errors
Error A2168: General Failure
deleted
>>>>>>>>>>>>>>> codegen.c comprdsp isn't initialised <<<<<<<<<<<<<<<<<<<<<<<<<<
int_8 comprdsp = 0; <<<<<<<<<<<<<<<<<<<<< modif
result on simple.asm ;habran source avx512 with
.686P
.XMM
.MMX
;
.x64 ; -pe requires to set cpu, model & language
option casemap : none
option win64 : 11
option frame : auto
option STACKBASE : RSP
;**************************************************************************************
HJWasm v2.13, Jan 29 2016, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
simple.asm: 9448 lines, 2 passes, 183 ms, 0 warnings, 0 errors
56 items in symbol table, expected 56
max items in a line=1, lines with 0/1/<=5/<=10 items=7953/56/0/0,
2049 items in resw table, max items/line=7 [0=662 1=688 376 114 42 11 5 2]
invokation CATSTR=0 SUBSTR=0 SIZESTR=0 INSTR=0 EQU(text)=2
lines read(files)/processed in pass one: 9447 / 9448
invokations: PreprocessLine=9502/9338/9333, Tokenize=18739/0
memory used: 1174 kB
There has been an error while assembling this project.
Appuyez sur une touche pour continuer...
;*************************************************************************************
deleted
Hello johnsa and habran,
First of all, many thanks for your nice work. Any plan later to add import libraries to your website terraspace.co.uk?
You are welcome Vortex :biggrin:
Johnsa will be able to answer that question about import libraries.
nidud, I was having the same thoughts as you, so I tested it with your code and works fine, so we will replace existing
code with yours
Thanks :t
I read last days posts with phone. Now, back to civilization I download the source.
HJWAsm32 compiled apparently perfect with Mingw32-gcc.
Testing my main Masm32-ObjAsm32-SimplMath project there is a problem in k1-4:
neqqu equ 56
DefineVariable k1 , REAL8 , neqqu dup (0.0);
DefineVariable k2 , REAL8 , neqqu dup (0.0);
DefineVariable k3 , REAL8 , neqqu dup (0.0);
DefineVariable k4 , REAL8 , neqqu dup (0.0);
Are k1, etc reserved words now?
Thanks. HSE
I found in special.h, they are some AVX things. I'm going to change my test code.
Test compilation is perfect now. I don't see any problem (remember I'm using max line len 1600, max id len 1580 and max macros nesting 120).
Quote from: HSE on January 30, 2016, 10:11:09 AM
I read last days posts with phone. Now, back to civilization I download the source.
HJWAsm32 compiled apparently perfect with Mingw32-gcc.
Testing my main Masm32-ObjAsm32-SimplMath project there is a problem in k1-4:
neqqu equ 56
DefineVariable k1 , REAL8 , neqqu dup (0.0);
DefineVariable k2 , REAL8 , neqqu dup (0.0);
DefineVariable k3 , REAL8 , neqqu dup (0.0);
DefineVariable k4 , REAL8 , neqqu dup (0.0);
Are k1, etc reserved words now?
Thanks. HSE
I found in special.h, they are some AVX things. I'm going to change my test code.
Test compilation is perfect now. I don't see any problem (remember I'm using max line len 1600, max id len 1580 and max macros nesting 120).
Hi,
k1 etc.. would be reserved now as registers for AVX512F, so you are correct.
Quote from: nidud on January 30, 2016, 06:10:31 AM
Quote
warning #2110: Initializer exceeds bit-field width.
You may try this in parser.h:
#define W1 0x8000
struct instr_item {
unsigned char opclsidx; /* v2.06: index for opnd_clstab */
unsigned char byte1_info; /* flags for 1st byte */
#if 1
unsigned short allowed_prefix; /* allowed prefix */
unsigned char first; /* 1=opcode's first entry */
unsigned char rm_info; /* info on r/m byte */
unsigned char opnd_dir; /* operand direction */
#else
unsigned char
allowed_prefix : 3, /* allowed prefix */
first : 1, /* 1=opcode's first entry */
rm_info : 3, /* info on r/m byte */
opnd_dir : 1; /* operand direction */
#endif
unsigned short prefix; /* used for EVEX */
unsigned short cpu;
unsigned char opcode; /* opcode byte */
unsigned char rm_byte; /* mod_rm_byte */
};
W1 is used as .prefix but a copy is stored in .allowed_prefix.
Hi,
This change is in (with Habrans verification too) and is in github.
I can from my side now report a completely successful build using both Visual C and GCC (I no longer have warnings about truncation.
I've included an initial value for comprdsp (to see if that helps with ToutEnMasm issue.
That being said, using the GCC built version I still get a general failure assembling simple.asm, which works fine with the Visual C build.
The line causing it:
simple.asm (1125):
vgatherdpd zmm15{k1}, [r14+ymm31*8+7bh] ;// 62 02 FD 41 92 B4 FE 7B 00 00 00
My other projects (not using any avx512f) seem to assemble and work perfectly with both.
Quote from: Vortex on January 30, 2016, 06:38:05 AM
Hello johnsa and habran,
First of all, many thanks for your nice work. Any plan later to add import libraries to your website terraspace.co.uk?
Import libraries for? (Sorry early in the morning and I'm not fully awake yet :) )
Hello johnsa,
I mean, a batch file or a tool to create the import libraries from module definition files. You could convert a set of import libraries to .def files.
The purpose is to supply HJWASM with include files and import libraries.
As far as I remember you are the one who can do that, can't you?
WinInc208 already have those?
You are right TWell, but maybe Vortex meant something else.
Quote from: johnsa on January 30, 2016, 08:26:46 PM
...
I can from my side now report a completely successful build using both Visual C and GCC (I no longer have warnings about truncation.
...
Travis GCC build #11 still reports one warning:
Quote
directiv.c: In function 'IncBinDirective':
directiv.c:269:8: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
see https://travis-ci.org/Terraspace/HJWasm/jobs/105851593
Sure,
linux users without wine needs pe-coff implib tool for cross compiling.
Quote from: GoneFishing on January 30, 2016, 10:04:59 PM
Quote from: johnsa on January 30, 2016, 08:26:46 PM
...
I can from my side now report a completely successful build using both Visual C and GCC (I no longer have warnings about truncation.
...
Travis GCC build #11 still reports one warning:
Quote
directiv.c: In function 'IncBinDirective':
directiv.c:269:8: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
see https://travis-ci.org/Terraspace/HJWasm/jobs/105851593
I can live with that one.. ? (I don't even capture the return value).
Quote from: Vortex on January 30, 2016, 09:03:37 PM
Hello johnsa,
I mean, a batch file or a tool to create the import libraries from module definition files. You could convert a set of import libraries to .def files.
The purpose is to supply HJWASM with include files and import libraries.
Do you mean to include wininc with hjwasm (but instead of just the asm include files you want the lib's too?)
Quote from: johnsa on January 31, 2016, 12:22:32 AM
[...
I can live with that one.. ? (I don't even capture the return value).
Me too ... but no warnings at all sounds so exciting ;)
Today I take my day off and what about you ?
Quote from: johnsa on January 31, 2016, 12:22:32 AM
Quote from: GoneFishing on January 30, 2016, 10:04:59 PM
Quote from: johnsa on January 30, 2016, 08:26:46 PM
...
I can from my side now report a completely successful build using both Visual C and GCC (I no longer have warnings about truncation.
...
Travis GCC build #11 still reports one warning:
Quote
directiv.c: In function 'IncBinDirective':
directiv.c:269:8: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
see https://travis-ci.org/Terraspace/HJWasm/jobs/105851593
I can live with that one.. ? (I don't even capture the return value).
I fixed it anyway, build should be clean now. :)
Yeah :t
https://travis-ci.org/Terraspace/HJWasm/jobs/105877377
[EDIT] ... Cheers !!! ...
Anyone on 64bit linux (and can/wants to test the hjwasm executable):
I've added the Travis-CI GCC x64 build to continuous deployment via S3, and the link directly to the executable is now on the website.
http://www.terraspace.co.uk/hjwasm.html (http://www.terraspace.co.uk/hjwasm.html)
Habran has also extended the contents of the usertype file and that is uploaded too (v1.1)
Quotefile ./hjwasm
./hjwasm: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=db10ed3597322da02cab0a05f1b3be3c77dddd83, stripped
Quote./hjwasm -elf64 simple.asm
HJWasm v2.13, Jan 30 2016, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
simple.asm: 9442 lines, 3 passes, 58426 ms, 0 warnings, 0 errors
Quote./hjwasm -?
HJWasm v2.13, Jan 30 2016, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
HJWasm [options] asm-file [options] [asm-file] ... [@env_var]
options:
-<0|1|..|10>[p] Set CPU: 0=8086 (default), 1=80186, 2=80286, 3=80386,
4=80486, 5=Pentium, 6=PPro, 7=P2, 8=P3, 9=P4, 10=x86-64;
<p> allows privileged instructions
-c Assemble without linking (always set)
-C<p|u|x> Set OPTION CASEMAP: p=NONE, u=ALL, x=NOTPUBLIC (default)
-D<name>[=text] Define text macro
-e<number> Set error limit number (default=50)
-EP Output preprocessed listing to stdout
-eq don't display error messages
-Fd[=<file_name>] Write import definition file
-Fi<file_name> Force <file_name> to be included
-Fl[=<file_name>] Write listing file
-Fo<file_name> Set object file name
-Fw<file_name> Set errors file name
-FPi 80x87 instructions with emulation fixups
-FPi87 80x87 instructions (default)
-fpc Disallow floating-point instructions (.NO87)
-fp<n> Set FPU, <n> is: 0=8087 (default), 2=80287, 3=80387
-G<c|d|r|z> Use Pascal, C, Fastcall or Stdcall calling convention
-I<directory> Add directory to list of include directories
-m<t|s|c|m|l|h|f> Set memory model:
(Tiny, Small, Compact, Medium, Large, Huge, Flat)
-nc=<name> Set class name of code segment
-n<d|m|t>=<name> Set name of d)ata segment, m)odule or t)ext segment
-q, -nologo Don't display version and copyright information
-Sa Maximize source listing
-safeseh Assert all exception handlers are declared
-Sf Generate first pass listing
-Sg Display generated code in listing
-Sn Suppress symbol-table listing
-Sx List false conditionals
-w Same as /W0 /WX
-W<number> Set warning level number (default=2, max=4)
-WX Treat all warnings as errors
-X Ignore INCLUDE environment path
-zcm C names are decorated with '_' prefix (default)
-zcw No name decoration for C symbols
-Zd Add line number debug info (OMF & COFF only)
-Zf Make all symbols public
-zf<0|1> Set FASTCALL type: 0=MS VC style (default),
1=OW register calling convention
-Zg Generated code is to exactly match Masm's one
-Zi[0|1|2|3] Add symbolic debug info (OMF & COFF): 0=globals
1= +locals, 2= +types (default), 3= +constants
-zlc No OMF records about data in code
-zld No OMF records about far call optimization
-zl<f|p|s> Suppress items in COFF symbol table: f=no .file entry,
p=no static procs, s=no auxiliary entries for sections
-Zm Masm v5.1 compatibility
-Zne Disable syntax extensions not supported by Masm
-Zp[n] Set structure alignment, n=<1|2|4|8|16|32>
-Zs Perform syntax check only
-zt<0|1|2> Set STDCALL symbol decoration: 0=No name decoration,
1=No '@size' suffix for functions, 2=Full (default)
-Zv8 Enable Masm v8+ PROC visibility
-zze No name decoration for exported symbols
-zzs Store decorated name of start address (COFF only)
@env_var Environment variable or file containing further commands
output formats:
-bin plain binary file
-coff COFF object file
-elf 32-bit ELF object file
-elf64 64-bit ELF object file
-mz DOS MZ binary file
-omf OMF object file (default)
-pe PE binary file, 32/64-bit
-win64 64-bit COFF object file
Well that looks promising :)
Hey guys,
You can have more than 1 topic, that's what the sub forum is for, HJWASM. :biggrin:
Quote from: johnsa on January 31, 2016, 12:33:05 AM
Quote from: Vortex on January 30, 2016, 09:03:37 PM
Hello johnsa,
I mean, a batch file or a tool to create the import libraries from module definition files. You could convert a set of import libraries to .def files.
The purpose is to supply HJWASM with include files and import libraries.
Do you mean to include wininc with hjwasm (but instead of just the asm include files you want the lib's too?)
Hello johnsa,
TWell is right. WinInc208 is containing all the necessary batch files to create the import libraries. I missed that. Thanks for your help.
Hi,
Github and binary packages on the website updated (31st Jan) to include the DR(x) register fix.
Cheers,
John
GCC Release : no warnings
GCC Debug :
reswords.c: In function 'DumpResWords':
reswords.c:1304:3: warning: format '%u' expects argument of type 'unsigned int', but argument 2 has type 'long unsigned int' [-Wformat=]
printf("\nitems in InstrTable[]: %u\n", sizeof(InstrTable) / sizeof(InstrTable[0]));
^
reswords.c:1306:5: warning: format '%u' expects argument of type 'unsigned int', but argument 2 has type 'long unsigned int' [-Wformat=]
sizeof(optable_idx) / sizeof(optable_idx[0]), INS_FIRST_1 + 1, sizeof(ResWordTable) / sizeof(ResWordTable[0]) - 1);
^
reswords.c:1306:5: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'long unsigned int' [-Wformat=]
gcc -c -IH -D__UNIX__ -DDEBUG_OUT -g -o GccUnixD/safeseh.o safeseh.c
gcc -c -IH -D__UNIX__ -DDEBUG_OUT -g -o GccUnixD/segment.o segment.c
gcc -c -IH -D__UNIX__ -DDEBUG_OUT -g -o GccUnixD/simsegm.o simsegm.c
gcc -c -IH -D__UNIX__ -DDEBUG_OUT -g -o GccUnixD/string.o string.c
gcc -c -IH -D__UNIX__ -DDEBUG_OUT -g -o GccUnixD/symbols.o symbols.c
symbols.c: In function 'DumpSymbol':
symbols.c:807:5: warning: format '%p' expects argument of type 'void *', but argument 5 has type 'union <anonymous>' [-Wformat=]
printf( "%-12s %16" I64_SPEC "X %02X %8p %c %8p %s\n", type, value, sym->mem_type, dir->e, sym->ispublic ? 'X' : ' ', sym->name, sym->name );
^
Should I continue posting in this thread ?
I'll have a look into these tomorrow :) I guess 15 pages is enough, we should start a new thread.
ok :)
Updates:
1) vzeroall is now working, no longer encoding as vzeroupper
2) intptr_t has been replaced with size_t and seems to prevent build warnings and general failures during assembly on Win7,8.1 and 10.
3) vpsllq operands are now the right way around
4) HIGHWORD is working
5) OPATTR changes moved from switch -Zg to -Zne
OPATTR is working (more compatibly - string literals will return 0, immediates - 36) with switch -Zne
6) VBROADCASTSD needs VEX.W=0, fixed to produce C4 E2 7D 19 01 instead of C4 E2 FD 19 01
7) A new OPTION EVEX:{0|1} has been added to enable assembly of avx512 code and the use of it's extended registers, previously hjwasm would accept zmm{n} or xmm16+
We're hoping that this already yields some performance increase in assembly time, but having it in place allows further optimisation back to original performance for non-AVX512 code.
8) Several issues from the regression tests fixed:
- SHLD syntax error
- ALIGN warning
9) Several other avx encoded shifts have corrected encodings.
10) We will be doing a full analysis of remaining AVX/VEX encodings and applying fixes for VPBROADCASTB/W/D today or tomorrow.
If anyone feels like testing the performance again to see if the evex option has had any impact yet.
With this:@SET SRC=..\HJWasm-master
@SET CC=gcc -c -m64 -I..\HJWasm-master\H -DWIN64=1 -DDEBUG_OUT=1
@REM hjwasm64.exe:
for %%c in (%SRC%\*.c) do %CC% %%c
gcc -s main.o apiemu.o assemble.o assume.o atofloat.o backptch.o bin.o branch.o cmdline.o codegen.o coff.o condasm.o context.o cpumodel.o data.o dbgcv.o directiv.o elf.o end.o equate.o errmsg.o expans.o expreval.o extern.o fastpass.o fixup.o fpfixup.o hll.o input.o invoke.o label.o linnum.o listing.o loop.o lqueue.o macro.o mangle.o memalloc.o msgtext.o omf.o omffixup.o omfint.o option.o parser.o posndir.o preproc.o proc.o queue.o reswords.o safeseh.o segment.o simsegm.o string.o symbols.o tbyte.o tokenize.o trmem.o types.o -o hjwasm64.exe
only these warnings and note:C:\HJWasm\gcc>gcc -c -m64 -I..\HJWasm-master\H -DWIN64=1 -DDEBUG_OUT=1 ..\HJWasm-master\trmem.c
..\HJWasm-master\trmem.c: In function 'formCodePtr':
..\HJWasm-master\trmem.c:187:26: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
..\HJWasm-master\trmem.c: In function 'trPrt':
..\HJWasm-master\trmem.c:219:41: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
..\HJWasm-master\trmem.c:233:37: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
..\HJWasm-master\trmem.c: In function 'tm_Init':
..\HJWasm-master\trmem.c:777:19: warning: passing argument 6 of '_trmem_open' from incompatible pointer type [enabled by default]
..\HJWasm-master\trmem.c:345:12: note: expected 'void (*)(struct FILE *, const char *, size_t)' but argument is of type 'void (*)(struct FILE *, const char *, unsigned int)'
Version 3 Feb tested, opattr issues are OK now :t
(except the -dword ptr [ebx], of course)
No changes in speed, virtually identical +- 0.1% compared to version 2 Feb.
Ok thanks for testing that!
With some thought we should be able to make use of this option now to reduce the overhead of all the evex testing!
V2.14 is available for download!
Changes:
1) Some bug fixes and improvements to stack frame generation in x64.
2) Fixed a tokenization bug with C-style hex immediate values, so you can now use 0x.. style without issue in place of H.
3) (The big one): .SWITCH support added (Thank's to Habran's huge effort here, it will use if/else for <=4 cases, otherwise depending on the range of case values use a jump table or non-recursive binary search) so it's pretty optimal and similar to how you'd expect a decent C/C++ compiler to generate switch.
John
Hello johnsa,
The download links are still pointing the old version 2.13 :
http://www.terraspace.co.uk/hjwasm213_x86.zip
http://www.terraspace.co.uk/hjwasm213_x64.zip
Hi Vortex,
You have to reload a page, it happened to me as well
Click with the right button and chose 'reload', I suppose you know that, but maybe someone else doesn't
Hi habran,
The problem is not reloading the page. The links are not updated. Move the mouse over the text hjwasm214_x86.zip and you will see that it points http://www.terraspace.co.uk/hjwasm213_x86.zip
You need to place the mouse cursor over this line :
QuoteHJWasm 2.14 (32bit) 10/04/2016 hjwasm214_x86.zip 32bit Binary Package (Windows)
Here is the screenshot :
http://vortex.masmcode.com/figs/screen.PNG
In the buttom of the screen capture, you will see the link to the zip file hjwasm213_x86.zip
You are right Vortex, it shows hjwasm13 but it is hjwasm14, just Johnsa forgot to change the name of folder
He will probably see this post and correct it.
However, hjwasm14 is inside and it works fine as it suppose to do 8)
Thanks for reporting it, good eyes mate :t
Yes, text is changed but link is to http://www.terraspace.co.uk/hjwasm213_x86.zip and http://www.terraspace.co.uk/hjwasm213_x64.zip
Here are the direct links that work:
http://www.terraspace.co.uk/hjwasm214_x86.zip
http://www.terraspace.co.uk/hjwasm214_x64.zip
My bad!
Fixed now :)
Thanks habran, I downloaded v2.14
Hi,
2.14 Update published today into git and binary packages on the site.. changes are:
1) Checking for repetition of cases so that it will report an error if case already exists in the switch block
2) Improve allocation of memory for cases in SWITCH and avoiding 64bit variables in hex2dec (caused general failure of 32bit version).
3) Bug fix for /Zi switch in 32bit.
Example switch now using character constants:
mov rax, "oword"
.switch rax
.case "byte"
mov rdx, "byte"
.break
.case "word"
mov rdx, "word"
.break
.case "dword"
mov rdx, "dword"
.break
.case "qword"
mov rdx, "qword"
.break
.case "oword"
mov rdx, "oword"
.break
.default
mov edx, 0
.break
.endswitch
The HIGHWORD operator is still broken:
x = -1
%echo @CatStr(%HIGH32 (HIGHWORD (x SHL 32)))
Should return zero. Use opnd1->llvalue for storing the result.
[[You might also correct your gitignore file, because directories are wrongly specified which cause build files to be added to version control]]
qWord, do you mean here:
Quoteif( opnd2->instr != EMPTY ) {
if ( opnd2->sym ) {
switch ( opnd2->instr ) {
case T_LOW:
case T_HIGH:
opnd1->llvalue = 1;
break;
case T_LOWWORD:
case T_HIGHWORD:
//case T_SEG: /* masm returns 0 for TYPE SEG <label>! */
opnd1->llvalue = 2;
break;
#if LOHI32
case T_LOW32:
case T_HIGH32:
opnd1->llvalue = 4;
break;
#endif
In in function highword_op (https://github.com/Terraspace/HJWasm/blob/master/expreval.c#L1548) convert line
Quote from: https://github.com/Terraspace/HJWasm/blob/master/expreval.c#L1557opnd1->value = (opnd1->value >> 16) & 0xFFFF; /* ASMC v2.14 (fix borrowed from nidud) */
to
Quoteopnd1->llvalue = (opnd1->value >> 16) & 0xFFFF; /* ASMC v2.14 (fix borrowed from nidud) */
Thanks qWord, will be fixed in next release :t