The MASM Forum

Specialised Projects => Assembler/Compiler Technology => Topic started by: japheth on April 20, 2013, 07:03:45 PM

Title: JWasm v2.10
Post by: japheth on April 20, 2013, 07:03:45 PM

Hello,

JWasm v2.10 has been released today: http://sourceforge.net/projects/jwasm/?source=directory (http://sourceforge.net/projects/jwasm/?source=directory)

This release is dedicated to Margaret Thatcher, who died 12 days ago. I am - and always have been - a big fan of her ( and the Austrian school of economics ).

I'm going to take a break from jwasm development - there are currently no plans for new releases or features.
Title: Re: JWasm v2.10
Post by: habran on April 20, 2013, 08:21:33 PM
Thank you very much Andreas, you have indepted us with your excellent tools :eusa_clap:
that's why I can forgive you for being a big fan of Margaret Thatcher (Iron Lady) ;)
No one is perfect :P
Title: Re: JWasm v2.10
Post by: Vortex on April 20, 2013, 08:38:20 PM
Thanks for the new release.
Title: Re: JWasm v2.10
Post by: Gunther on April 20, 2013, 08:53:34 PM
Andreas,

thank you for the release. :t

Gunther
Title: Re: JWasm v2.10
Post by: Siekmanski on April 20, 2013, 09:16:35 PM
Thanks  :t
Title: Re: JWasm v2.10
Post by: ToutEnMasm on April 20, 2013, 10:12:17 PM
Thanks.he is better  than ml.  :t

Title: Re: JWasm v2.10
Post by: jj2007 on April 20, 2013, 11:58:41 PM
My two biggest sources (15 and 19kLines) assemble perfectly with JWasm. I get an Error A2048 with #3, however - and it worked with JWasm of 15 March :(

Will investigate, and find a workaround. In any case, JWasm is a great achievement: 99.9% compatible, free and free from restrictions, and twice as fast as ML.exe...

My sincere compliments to Japheth :t
Title: Re: JWasm v2.10
Post by: dedndave on April 21, 2013, 01:50:38 AM
there seems to be a few google hits on "jwasm error A2048", Jochen
maybe they will help
Title: Re: JWasm v2.10
Post by: jj2007 on April 21, 2013, 02:27:13 AM
No need for Google, Dave ;-)

include \masm32\include\masm32rt.inc

MyStruct STRUCT
  msBytes   db 100, 200
MyStruct   ENDS

.code
ms MyStruct <>
start:
   mov ecx, 1
   movzx eax, ms.msBytes[ecx]
   print str$(eax), 9

   if (type ms.msBytes[ecx]) eq BYTE
      inkey "a byte", 13, 10
   else
      inkey "NOT a byte", 13, 10
   endif
   exit
end start
Title: Re: JWasm v2.10
Post by: qWord on April 21, 2013, 03:09:34 AM
great!

(Even if it currently does not support all of MASM's obscure "type-features"  :bgrin:)
Title: Re: JWasm v2.10
Post by: jj2007 on April 21, 2013, 03:13:00 AM
(Even if it currently does not support all of MASM's obscure "type-features"  :bgrin:)

Psssst! If there a C coders around, they might be offended!
Title: Re: JWasm v2.10
Post by: Gunther on April 21, 2013, 03:45:29 AM
Jochen,

Psssst! If there a C coders around, they might be offended!

do you really think that here are C coders around?  :lol: It's an assembly language forum, you know.

Gunther
Title: Re: JWasm v2.10
Post by: Jibz on April 21, 2013, 07:07:45 AM
do you really think that here are C coders around?  :lol: It's an assembly language forum, you know.

*shifty eyes*

:biggrin:
Title: Re: JWasm v2.10
Post by: Gunther on April 21, 2013, 07:52:39 PM
Good answer, Jibz.

Gunther
Title: Re: JWasm v2.10
Post by: Ficko on April 22, 2013, 05:24:11 PM
Thanks "Japheth", great work. :t

"I'm going to take a break from jwasm development"

Does this mean we do not need to bother you with bugreports anymore will be ignored anyway?
Title: Re: JWasm v2.10
Post by: japheth on April 22, 2013, 08:04:31 PM
Thanks all for feedback!

> Does this mean we do not need to bother you with bugreports anymore will be ignored anyway?

No. It might take longer until they got fixed, though.
Regressions in v2.10 compared to v2.09 will be fixed ASAP - and if there's a serious one, I'll make a v2.10a.

> (Even if it currently does not support all of MASM's obscure "type-features"  :bgrin:)

A full fix would have required some major changes/clean-ups in the expression evaluator - this has to wait.

> I get an Error A2048 with #3, however - and it worked with JWasm of 15 March :(

Yes, it's indeed a ( minor  :icon_mrgreen: ) regression. If you find another one I'll do a v2.10a.

> that's why I can forgive you for being a big fan of Margaret Thatcher (Iron Lady) ;)

I forgive you too. And don't worry, there surely won't be any releases dedicated to Obama or Faehnlein-Angie ( the latter is a local term only comprehensible to native German speakers ).
Title: Re: JWasm v2.10
Post by: habran on April 22, 2013, 09:23:06 PM
I don't like damn politisions
they are divided in: The Good, the Bad and the Ugly :biggrin:
and very often combination of Bad & Ugly :lol:
Title: Re: JWasm v2.10
Post by: ToutEnMasm on April 24, 2013, 03:17:35 PM

There is a mystere here with DLLIMPORT :
Where is the object file ?
Link don't find it but create the executable ?????

Title: Re: JWasm v2.10
Post by: Jibz on April 24, 2013, 07:04:20 PM

There is a mystere here with DLLIMPORT :
Where is the object file ?
Link don't find it but create the executable ?????

I don't know how JWasm works, but a quick google found:

http://www.japheth.de/JWasm/Manual.html#OPTDLLIMPORT
http://www.japheth.de/JWasm/Manual.html#OUTPUTFORMATPE

which seem to indicate that for the PE output format, it simply writes the declarations from DLLIMPORT into the imports section of the executable, and thus does not need any import library or object file. I think fasm works pretty much the same way.
Title: Re: JWasm v2.10
Post by: ToutEnMasm on April 24, 2013, 08:58:33 PM

Thanks for answer , an object file is useful for debugging.

This one is a problem,compiled OK by ML but show a bug with Jwasm.
Compiled with Jwasm the "Edit"---> "trouve" menu made a crash.
Title: Re: JWasm v2.10
Post by: japheth on April 24, 2013, 09:05:45 PM
There is a mystere here with DLLIMPORT :
Where is the object file ?

There's probably no mystery, but a bit confusion: it makes no sense to specify both -coff and -pe in the command line. Option -coff makes jwasm write the output in the MS COFF object format, while -pe makes jwasm write the output in the PE binary format. You can't have both formats at the same time.

As for OPTION DLLIMPORT: this option may be useful for both -coff and -pe.  However, the purpose is slightly different: for -pe, it allows to resolve external references without using a linker, while for -coff it may allow external references without the need of import libraries ( the latter works for jwlink only, because MS link does no longer support the IMPORTS statement in module definition files ).
Title: Re: JWasm v2.10
Post by: anunitu on April 24, 2013, 09:57:54 PM
japheth,I completely understand the take a break from things. Real life still can be demanding,and even when one loves what they do as a sideline,then there is also the "Ohhh shiny" factor,where something (or someone)
catches your attention. Work is one thing and hobby's,but some real world stuff can be SOOOO much fun.
Title: Re: JWasm v2.10
Post by: dedndave on April 25, 2013, 01:26:52 AM
Quote
"Ohhh shiny" factor
as in Firefly ?
Title: Re: JWasm v2.10
Post by: anunitu on April 25, 2013, 01:33:16 AM
As in distracting Dave. I think we all have our "Shiny" moments be it that flashy car,or in Hutchs case that flashy blonde.