Author Topic: JWASM is updated.  (Read 28511 times)

Ficy

  • Guest
JWASM is updated.
« on: June 25, 2012, 02:14:38 AM »
Looks like "Japheth" is back from his grave. :greensml:

http://www.japheth.de/JWasm.html

jj2007

  • Member
  • *****
  • Posts: 7470
  • Assembler is fun ;-)
    • MasmBasic
Re: JWASM is updated.
« Reply #1 on: June 25, 2012, 03:46:38 AM »
Champagne :eusa_dance:

My fattest source (RichMasm) assembles fine, in 1000 ms against 1660 for ML6.15
MasmBasic shows little problems:
  pMRB equ <[4+edi.MESSAGE_RESOURCE_BLOCK]>
  mov edx, pMRB.LowId --->Error A2271: structure field expected
Besides, it still expands macros inside quoted text...

But otherwise, this is good news for the assembly community :biggrin:

Vortex

  • Member
  • *****
  • Posts: 1692
Re: JWASM is updated.
« Reply #2 on: June 25, 2012, 04:20:38 AM »
Hi Ficy,

Thanks for the good news :t

Greenhorn

  • Member
  • **
  • Posts: 93
Re: JWASM is updated.
« Reply #3 on: June 26, 2012, 01:19:28 AM »
Yep, this are very good news.  :eusa_dance:

KeepingRealBusy

  • Member
  • ***
  • Posts: 426
Re: JWASM is updated.
« Reply #4 on: June 26, 2012, 02:38:48 AM »
But still no source for this release.

Dave.

anta40

  • Member
  • ***
  • Posts: 293
Re: JWASM is updated.
« Reply #5 on: June 26, 2012, 02:49:27 AM »
Wait untill it reaches the stable version, then the source code will be released.
AFAIK that's the way Japheth does it.

KeepingRealBusy

  • Member
  • ***
  • Posts: 426
Re: JWASM is updated.
« Reply #6 on: June 27, 2012, 11:44:39 AM »
Hurray! He just touched my problem (from last Dec), will be fixed in version 7! He's back!

Dave.

johnsa

  • Member
  • ***
  • Posts: 463
    • Uasm
Re: JWASM is updated.
« Reply #7 on: June 27, 2012, 10:17:17 PM »
This is fantastic news!

I really hope we can get the CV8 debug info in and the changes Habran worked on. (This would certainly take the pressure of my own development, although I wouldn't stop just because jwasm is complete for my needs).

Greenhorn

  • Member
  • **
  • Posts: 93
Re: JWASM is updated.
« Reply #8 on: July 03, 2012, 04:12:35 AM »
I really hope we can get the CV8 debug info in and the changes Habran worked on.

The wrong offset calculation of LOCALs is fixed, but if you mean the mean the manipulation of RSP before/after every INVOKE I'm not sure.
There seems to be a Bug Tracker on this issue, but Japheth stated in the comment that he don't understand what is meant.
So, the author of this Tracker should get more specific about it ...

BTW, JWasm 2.07rc2 is out ...  :t

jcfuller

  • Member
  • **
  • Posts: 175
Re: JWASM is updated.
« Reply #9 on: July 03, 2012, 05:43:07 AM »
BTW, JWasm 2.07rc2 is out ...  :t

Looks to be 2.07rc3.

James

Greenhorn

  • Member
  • **
  • Posts: 93
Re: JWASM is updated.
« Reply #10 on: July 03, 2012, 05:45:27 AM »
Looks to be 2.07rc3.

Ooops, my fault. Yes, of course I meant the rc3...  :redface:

johnsa

  • Member
  • ***
  • Posts: 463
    • Uasm
Re: JWASM is updated.
« Reply #11 on: July 03, 2012, 04:56:25 PM »
I'm referring to the RSP modification before/after every invoke as well as actual CodeView V8 format symbolic debug info in the OBJ file so you can actually debug a project :)
I spoke to Japheth and he says it might be a feature for 2.08 .. I can't stress how important it is.. I really wish it would just get done already.

anta40

  • Member
  • ***
  • Posts: 293
Re: JWASM is updated.
« Reply #12 on: July 06, 2012, 06:41:15 PM »
the final release of 2.7 is now available  ;)

Greenhorn

  • Member
  • **
  • Posts: 93
Re: JWASM is updated.
« Reply #13 on: July 08, 2012, 05:48:20 AM »
japheth compiled a x64 binary of JWasm, but he states that it is slower than the x86 binary...

http://sourceforge.net/projects/jwasm/forums/forum/927109/topic/5409021

Ficko

  • Regular Member
  • *
  • Posts: 38
Re: JWASM is updated.
« Reply #14 on: July 13, 2012, 06:38:27 AM »
There is a preliminary "208bw" to be tested at http://www.japheth.de/Download/JWasm/

Quote
   Bugfixes:
   -  forward references of structures in an expression may have failed
      (see regression test assume7.aso).
   -  if C-style expressions in runtime conditional directives were too
      complicated, the generated code may have caused 'symbol not defined'
      errors.