2. our listing format 3. macro 1. how to compile an asm file

0x9b 0x97 0x37 0x00 0x000000008000002a : slliw a5,a5,0x3

`@JennyTse` help me fix it

"OUTS" instruction is stated in Intel manual, but NASM doesn't support the 'LODS', 'MOVS', 'STOS', 'SCAS', 'CMPS', 'INS', or 'OUTS' instructions, but only supports the forms such as 'LODSB', 'MOVSW', and 'SCASD' which explicitly specify the size of the components of the strings being manipulated. https://www.conradk.com/codebase/2017/06/06/x86-64-assembly-from-scratch/ **I need to know the reason**

jmp [cx] does not exist in the list, but should we give an error if it is typed by a user? Currently only have a blank result, reason behind is not because there is no error message for such case, but because "no viable alternative input", which means the parser cant even identify it.


In the function "NOP EAX" (16 bit mode), opcode is NP... which may mean no prefix. In nasm, it turns out that the instruction opcode is 66 f 1f c0. What is 66 if it is not a prefix?

POP r64 should contain REX Prefix. However, nasm doesn't output the prefix for some r64 registers. Example: 1. pop rax: quantr = 40 58, nasm = 58 2. pop r10: quantr = 41 5a, nasm = 41 5a 40, 41 in the above example are the REX prefix.

Why nasm supports reg64 in LAR instruction, mismatch with intel manual?

Jenny: make sure if all instructions calling all 5 functions are still works: * initLeftToken * leftInit * initRightToken * rightInit * initCondition * initIns Kelvin: Remove byte/word/dword/qword from indirect memory access, i mean the wording before []

Hi, you can use this tool to compare any changes of the PE file header/section values as shown like this:    download here: [LPE-DLXb_1.41_UPD.zip](/uploads/33a8cb7f7bb5b1ac02313d12f8cbcb1d/LPE-DLXb_1.41_UPD.zip)

Same to PEView, but I think powerful than each other.  You can download the Explorer Suite and install : [ExplorerSuite.exe](/uploads/27e6c712d825c27e319ad98744d1d438/ExplorerSuite.exe)

build by: **cl smallPE.c** guess that it will include import table Kernel32.dll reference [smallPE.c](/uploads/befec26eceff3131e17a905091d9b0ec/smallPE.c) [smallPE.exe](/uploads/fe1009c4e9b752d9ee7d8b94e1a838f2/smallPE.exe)

check the PE header field by PE View build by: **cl /nologo /c smallPE.c** **link /nologo /ENTRY:main /NODEFAULTLIB /SUBSYSTEM:WINDOWS smallPE.obj** [smallPE.exe](/uploads/c4e24b53e726d8043aa0b62bfab17c7c/smallPE.exe) [smallPE.c](/uploads/3a3cfde18ae3070bb919cf6677618eb3/smallPE.c)

Enhance netbeans-antlr to support antlr file formatting

1. Zero padding, cut of pad "0" 2. Jenny consolidate your code into well format, let us understand and give us tutorial next sat morning 3. Desmond: a. nasm in linux example, able to run and print hello world https://cs.lmu.edu/~ray/notes/nasmtutorial/ b. find out the minimum requirement to stuck asm program and run in linux

./asm/assemble.c . Nasm just have these error, not many. ``` switch (m) { case MERR_OPSIZEMISSING: nasm_error(ERR_NONFATAL, "operation size not specified"); break; case MERR_OPSIZEMISMATCH: nasm_error(ERR_NONFATAL, "mismatch in operand sizes"); break; case MERR_BRNOTHERE: nasm_error(ERR_NONFATAL, "broadcast not permitted on this operand"); break; case MERR_BRNUMMISMATCH: nasm_error(ERR_NONFATAL, "mismatch in the number of broadcasting elements"); break; case MERR_MASKNOTHERE: nasm_error(ERR_NONFATAL, "mask not permitted on this operand"); break; case MERR_DECONOTHERE: nasm_error(ERR_NONFATAL, "unsupported mode decorator for instruction"); break; case MERR_BADCPU: nasm_error(ERR_NONFATAL, "no instruction for this cpu level"); break; case MERR_BADMODE: nasm_error(ERR_NONFATAL, "instruction not supported in %d-bit mode", bits); break; case MERR_ENCMISMATCH: nasm_error(ERR_NONFATAL, "specific encoding scheme not available"); break; case MERR_BADBND: nasm_error(ERR_NONFATAL, "bnd prefix is not allowed"); break; case MERR_BADREPNE: nasm_error(ERR_NONFATAL, "%s prefix is not allowed", (has_prefix(instruction, PPS_REP, P_REPNE) ? "repne" : "repnz")); break; case MERR_REGSETSIZE: nasm_error(ERR_NONFATAL, "invalid register set size"); break; case MERR_REGSET: nasm_error(ERR_NONFATAL, "register set not valid for operand"); break; default: nasm_error(ERR_NONFATAL, "invalid combination of opcode and operands"); ```

how do use these instructions? 

I still don't understand what situation we need to add 0x66 ? adc al,0x12 ``` bit 16 = 14 12 bit 32 = 14 12 bit 64 = 14 12 ``` adc ax,0x1234 ``` bit 16 = 15 34 12 bit 32 = 66 15 34 12 bit 64 = 66 15 34 12 ``` adc eax,0x12345678 ``` bit 16 = 66 15 78 56 34 12 bit 32 = 15 78 56 34 12 bit 64 = 15 78 56 34 12 ```

Please study windows object file format. Decode the byte like what you did last time. Please stop study ELF since i am creating a library for it. ``` global _main extern _GetStdHandle@4 extern _WriteFile@20 extern _ExitProcess@4 section .text _main: ; DWORD bytes; mov ebp, esp sub esp, 4 ; hStdOut = GetstdHandle( STD_OUTPUT_HANDLE) push -11 call _GetStdHandle@4 mov ebx, eax ; WriteFile( hstdOut, message, length(message), &bytes, 0); push 0 lea eax, [ebp-4] push eax push (message_end - message) push message push ebx call _WriteFile@20 ; ExitProcess(0) push 0 call _ExitProcess@4 ; never here hlt message: db 'Hello, World', 10 message_end: ``` To compile, you'll need NASM and LINK.EXE (from Visual studio Standard Edition) ``` nasm -fwin32 hello.asm link /subsystem:console /nodefaultlib /entry:main hello.obj ```