HJWasm Releases

[GoneFishing]

GCC build successful
No .32bit part , doesn't require  any editing
See atached log for warnings

[GoneFishing]

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 "/" .

[TouEnMasm]

The last version on github is OK for me (WINDOWS 10) ,no more FRAME problem

[Grincheux]

An update per day ok, every five minutes I can't

[johnsa]

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)

[johnsa]

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...

[Grincheux]

Hey.. 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

[GoneFishing]

It would be great if someone posted simple example with AVX512 instructions .
I want to compile and disasm it .

[habran]

Hi GoneFishing,
Here is an example with most AVX51F instructions

[johnsa]

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 ..

[GoneFishing]

Thank you, HABRAN
JOHNSA, I've already noticed it on GItHub  :t

[habran]

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?

[habran]

Hi Johnsa, there is no need to ask me for agreement, I trust you totally 8)

[GoneFishing]

HABRAN , I've done it !
I must say , that was really good SIMPLE example 
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:

simple.asm: 9442 lines, 3 passes, 55063 ms, 0 warnings, 0 errors

OW 1.9 32 bit:

simple.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

[johnsa]

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..