News:

Masm32 SDK description, downloads and other helpful links
Message to All Guests
NB: Posting URL's See here: Posted URL Change

Main Menu

Unified Extensible Firmware Interface (UEFI) Example

Started by LiaoMi, June 29, 2019, 04:04:18 AM

Previous topic - Next topic

johnsa

You need to use at least .686 to allow the simd instructions, at least it's always been this way in jwasm/uasm. .686 should then work for both uasm and masm.

I've changed MEMALIGN to ALIGNADDR .. makes sense and it shouldn't conflict with anything.

Updated the packages on the site.

aw27

Quote from: johnsa on October 21, 2019, 09:54:07 PM
I'm happy to remove the case sensitive version for this or rename it.. we can take a vote.
Personally I'd opt to rename it so that the case can be freely applied.

I don't know if this makes sense, but the assembler could simply supersede any internal macro whenever there is a user defined macro with the same name. This will prevent the need for another switch which people tend to forget (and UASM already has a large number of them to remember).

johnsa

Agreed, for now I'm going to leave it renamed so there is no immediate conflict.
I think in future I will add a flag to the definitions of the macro-lib marking them as "internal", so that we can override them with any user defined ones.

hutch--

 :biggrin:

> Actually MASM is taught in college and high-school and Masm32 is not allowed there.

You may be surprised just how many UNI courses use the MASM32 SDK and over how many years. Where MASM is taught at universities, it is usually DOS 16 bit and others use Kip Irvine's book and examples.

aw27

Quote from: hutch-- on October 21, 2019, 11:29:56 PM
:biggrin:
You may be surprised just how many UNI courses use the MASM32 SDK and over how many years. Where MASM is taught at universities, it is usually DOS 16 bit and others use Kip Irvine's book and examples.

:biggrin:
Bad luck, when I was doing online tutoring not a single one requested Masm32. For x86/x64 ASM, all of them required Irvine for 16, 32 and 64-bit.

hutch--

 :biggrin:

Bigger fool them, commerce dictates BUYING the software.  :tongue:

HSE

Quote from: AW on October 21, 2019, 11:46:23 PM
Bad luck, when I was doing online tutoring not a single one requested Masm32.
Then: MASM32 is very easy.  :biggrin:
Equations in Assembly: SmplMath

aw27

I suspect teachers were receiving a fat commission for doing classes based on the Irvine's book.  :badgrin:

TimoVJL

#53
 :sad:
May the source be with you

LiaoMi

Quote from: johnsa on October 21, 2019, 10:59:27 PM
You need to use at least .686 to allow the simd instructions, at least it's always been this way in jwasm/uasm. .686 should then work for both uasm and masm.

I've changed MEMALIGN to ALIGNADDR .. makes sense and it shouldn't conflict with anything.

Updated the packages on the site.

Hi johnsa,

I updated the cache, but the links are old  :icon_idea:

johnsa

I've only updated the packages not the site, just waiting for confirmation that initial testing was ok.

jj2007

John,
Where is the latest UAsm64.exe? The one with the memalign problem is 20 Oct 20:50.

TimoVJL

#57
 :sad:
May the source be with you

jj2007

Quote from: TimoVJL on October 22, 2019, 05:49:12 PM
UAsm 2.50 compiled with Clang 9 and using msvcrt.dll, so it's so slow.

Now it works, but it's indeed not that fast:
1750 ms  Uasm64msvcrt, ML 6.15 & 10.0
1500 ms  Uasm64
1150 ms  AsmC

TimoVJL

#59
clang 9 & libc
5.382s        asmc.exe 2.30.23
7.831s        uasm64libc.exe 2.50
8.393s        uasm64vc2019.exe 2.50
8.830s        uasm64.exe 2.49
9.235s        uasm64poc9.exe 2.50
10.124s       uasm32libc.exe 2.50

EDIT: fix WIN64
May the source be with you