News:

Masm32 SDK description, downloads and other helpful links
Message to All Guests

Main Menu

UASM 2.51

Started by johnsa, March 01, 2021, 01:14:16 AM

Previous topic - Next topic

KradMoonRa

Hi LiaoMi

/Oi /arch:AVX2

But i think it will not get significant improvement.

Installing masm32sdk and investigating all above...


windows:
Win Setup AVX2 Uninstall and Install again.
or
Win binaries files AVX2 Copy hover.

The uasmlib

TimoVJL

Quote from: LiaoMi on March 21, 2021, 09:39:56 PM
[Why is there a big difference in timing ?!  :dazzled:
Just a dynamic linking to vcruntime140.dll
If a your software is too fast, just link it with ucrt and those speed problems are gone :tongue:
May the source be with you

jj2007

Quote from: KradMoonRa on March 21, 2021, 10:25:38 PM
/Oi /arch:AVX2

Win binaries files AVX2
That's the crashing version. Above I attached a tiny demo that builds fine with MASM 6.14 and all others but doesn't work with your latest non-AVX2 UAsm.

KradMoonRa

Hi,

@jj2007
Chr$ macro has this error to my, figuring how to fix and test.

***********
ASCII build
***********

NewMasm32.asm(148) : Error A2056: Symbol already defined: NewString
Chr$(106)[NewMasm32.asm]: Macro called from
  NewMasm32.asm(148): Main line code

@LiaoMi

MemOut assembles fines after comment out missing fltlib.inc and rstrtmgr.inc from my masm32sdk

        include winspool.inc
        ;include fltlib.inc
        include secur32.inc
        ;include rstrtmgr.inc

The uasmlib

jj2007

See reply #41. No MasmBasic, just plain Masm32 SDK - and it throws errors.

LiaoMi

Quote from: KradMoonRa on March 21, 2021, 11:41:44 PM
Hi,

@jj2007
Chr$ macro has this error to my, figuring how to fix and test.

***********
ASCII build
***********

NewMasm32.asm(148) : Error A2056: Symbol already defined: NewString
Chr$(106)[NewMasm32.asm]: Macro called from
  NewMasm32.asm(148): Main line code

@LiaoMi

MemOut assembles fines after comment out missing fltlib.inc and rstrtmgr.inc from my masm32sdk

        include winspool.inc
        ;include fltlib.inc
        include secur32.inc
        ;include rstrtmgr.inc


@KradMoonRa the same thing after deleting these lines, as I already wrote, the number of include files affects the appearance of this error  :rolleyes:

UASM v2.51, Feb 27 2021, 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
***********

C:\masm32\include\winspool.inc(585) : Fatal error A1105: Out of Memory
Microsoft (R) Incremental Linker Version 14.28.29337.0
Copyright (C) Microsoft Corporation.  All rights reserved.

LINK : fatal error LNK1181: cannot open input file 'Test_x86.obj'
Press any key to continue . . .

KradMoonRa

Quote from: LiaoMi on March 22, 2021, 12:45:50 AM
Quote from: KradMoonRa on March 21, 2021, 11:41:44 PM
Hi,

@jj2007
Chr$ macro has this error to my, figuring how to fix and test.

***********
ASCII build
***********

NewMasm32.asm(148) : Error A2056: Symbol already defined: NewString
Chr$(106)[NewMasm32.asm]: Macro called from
  NewMasm32.asm(148): Main line code

@LiaoMi

MemOut assembles fines after comment out missing fltlib.inc and rstrtmgr.inc from my masm32sdk

        include winspool.inc
        ;include fltlib.inc
        include secur32.inc
        ;include rstrtmgr.inc


@KradMoonRa the same thing after deleting these lines, as I already wrote, the number of include files affects the appearance of this error  :rolleyes:

UASM v2.51, Feb 27 2021, 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
***********

C:\masm32\include\winspool.inc(585) : Fatal error A1105: Out of Memory
Microsoft (R) Incremental Linker Version 14.28.29337.0
Copyright (C) Microsoft Corporation.  All rights reserved.

LINK : fatal error LNK1181: cannot open input file 'Test_x86.obj'
Press any key to continue . . .



Something is wrong i can't direct reproduce in different system: just to debug trace the exit it ill help find the pointer in cause.
The uasmlib

nidud

#52
deleted

LiaoMi

Quote from: nidud on March 22, 2021, 01:21:27 AM
If you refer to the last version that is most likely the CV8 bug as this will trash random memory locations based on the number of source and include files.

The reason why this was not picked up earlier has to do with the size of the buffer as it is roomy enough for all the test cases used.

This may be tested by omitting the -Zi8 switch (assuming that is used in the test).

Hi nidud,

the compilation flag -Zi8 does not affect the error in this case. Fresh installation of masm32 really does not display any error.

@KradMoonRa Try to replace with this folder https://anonfiles.com/w9pdGflfu1/include_zip

jj2007

Quote from: LiaoMi on March 22, 2021, 02:17:34 AMFresh installation of masm32 really does not display any error.
What do you mean with this? Everybody should reinstall Masm32 to make UAsm work??

LiaoMi

Quote from: jj2007 on March 22, 2021, 02:19:54 AM
Quote from: LiaoMi on March 22, 2021, 02:17:34 AMFresh installation of masm32 really does not display any error.
What do you mean with this? Everybody should reinstall Masm32 to make UAsm work??

Hi jj2007,

:biggrin: :biggrin: :biggrin: these are my test results, nothing more, KradMoonRa has installed a fresh release, so I wanted to find out why he does not have a memory error in his case. The fact is, the previous version did not have this problem. I'm talking about my test sample, not your macro  :tongue: This means that my include files are different from the standard ones.

KradMoonRa

Yep, probably some weird binary symbol in text file...

LiaoMi
This inc files are 32bit or 64bits version?
The uasmlib

LiaoMi

Quote from: KradMoonRa on March 22, 2021, 02:32:17 AM
Yep, probably some weird binary symbol in text file...

LiaoMi
This inc files are 32bit or 64bits version?

32Bit only

UASM v2.51.2 Test results -> http://masm32.com/board/index.php?topic=9211.msg101525#msg101525
UASM v2.51.2, Mar 20 2021, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.

Translated Windows SDK 10.0 32 bits
test.asm: 129 lines, 2 passes, 2972 ms, 0 warnings, 0 errors
Microsoft (R) Incremental Linker Version 14.28.29337.0
Copyright (C) Microsoft Corporation.  All rights reserved.


Starting pass 1
test.obj : fatal error LNK1276: invalid directive 'lib:ucrt.lib' found; does not start with '/'
test.obj : warning LNK4209: debugging information corrupt; recompile module; linking object as if no debug info



KradMoonRa

Quote from: LiaoMi on March 22, 2021, 02:47:44 AM
Quote from: KradMoonRa on March 22, 2021, 02:32:17 AM
Yep, probably some weird binary symbol in text file...

LiaoMi
This inc files are 32bit or 64bits version?

32Bit only

Test results -> http://masm32.com/board/index.php?topic=9211.msg101525#msg101525
UASM v2.51.2, Mar 20 2021, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.

Translated Windows SDK 10.0 32 bits
test.asm: 129 lines, 2 passes, 2972 ms, 0 warnings, 0 errors
Microsoft (R) Incremental Linker Version 14.28.29337.0
Copyright (C) Microsoft Corporation.  All rights reserved.


Starting pass 1
test.obj : fatal error LNK1276: invalid directive 'lib:ucrt.lib' found; does not start with '/'
test.obj : warning LNK4209: debugging information corrupt; recompile module; linking object as if no debug info


Yep that is the error that @nidud has talking about, fixed Reply #31
The uasmlib

johnsa

Unfortunately#31 hasn't fixed my corrupt debug info yet. Annoyingly it is only occurring on a massive project, and as I comment lines out/add back in the result changes so it's near on impossible to pin it down :(
I think I'll just have to carry on ignoring it until I can find a reproducable test case of it.

LiaoMi, I tested your MemOut file and it works fine for me with uasm32 and uasm64? Perhaps someone else can try too.

KradMoonRa, I'm thinking it's very confusing that you've got a fork going of UASM with different version numbers and the same name, perhaps we could agree on a name change for your package ?
Maybe something like Kuasm (just a thought following tradition with the naming) ?