Error a2013 model must precede this directive

Tinkering around with MASM a bit, and I have no idea what these errors mean, or if I’m writing this code close to correctly. As it is written currently, it should just be greeting the user, asking for two numbers and saying goodbye (trying to get a skeleton working before doing any calculations or anything special).

INCLUDELIB Irvine32.inc ;  Note: line number 7


.data
userName    BYTE    33 DUP(0)   ;string to be entered by user
firstNumber DWORD   ?           ;integer to be entered by user
secondNumber    DWORD     ?         ;integer to be entered by user
intro_1     BYTE        "Elementary Arithmetic by Marshall Todt", 0
intro_2     BYTE        "Enter 2 numbers, and I'll show you the sum, difference,", 0
intro_3     BYTE        "product, quotient, and remainder.", 0
prompt_1        BYTE        "Enter the first integer: ", 0
prompt_2        BYTE        "Enter the second integer: ",0
goodBye     BYTE        "Impressed?  Bye!", 0

.code
main PROC

;Introduction
    mov     edx, OFFSET intro_1 
    call    WriteString
    call    CrLf
    move        edx, OFFSET intro_2
    call WriteString
    call CrLF
    move        edx, OFFSET intro_3
    call WriteString
    call CrLF

;Get the data
    mov     edx, OFFSET prompt_1
    call    WriteString
    call    ReadInt
    mov     firstNumber, eax
    mov     edx, OFFSET prompt_2
    call    WriteString
    call    ReadInt
    mov     secondNumber, eax



;Say "Good-bye"
    mov     edx, OFFSET goodBye
    call    WriteString
    call    CrLf
    exit    ; exit to operating system
main ENDP

END main

These are the errors i am getting:

Error   1   error A2013: .MODEL must precede this directive c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   10  1   Assignment1
Error   2   error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   11  1   Assignment1
Error   3   error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   12  1   Assignment1
Error   4   error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   13  1   Assignment1
Error   5   error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   14  1   Assignment1
Error   6   error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   15  1   Assignment1
Error   7   error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   16  1   Assignment1
Error   8   error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   17  1   Assignment1
Error   9   error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   18  1   Assignment1
Error   10  error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   19  1   Assignment1
Error   11  error A2013: .MODEL must precede this directive c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   21  1   Assignment1
Error   12  error A2034: must be in segment block : main    c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   22  1   Assignment1
Error   13  error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   25  1   Assignment1
Error   14  error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   26  1   Assignment1
Error   15  error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   27  1   Assignment1
Error   16  error A2008: syntax error : edx c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   28  1   Assignment1
Error   17  error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   29  1   Assignment1
Error   18  error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   30  1   Assignment1
Error   19  error A2008: syntax error : edx c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   31  1   Assignment1
Error   20  error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   32  1   Assignment1
Error   21  error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   33  1   Assignment1
Error   22  error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   36  1   Assignment1
Error   23  error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   37  1   Assignment1
Error   24  error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   38  1   Assignment1
Error   25  error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   39  1   Assignment1
Error   26  error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   40  1   Assignment1
Error   27  error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   41  1   Assignment1
Error   28  error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   42  1   Assignment1
Error   29  error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   43  1   Assignment1
Error   30  error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   48  1   Assignment1
Error   31  error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   49  1   Assignment1
Error   32  error A2034: must be in segment block   c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   50  1   Assignment1
Error   33  error A2008: syntax error : exit    c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   51  1   Assignment1
Error   34  error A1010: unmatched block nesting : main c:UsersMarshalldocumentsvisual studio 2010ProjectsSolution1Assignment1Assignment1.asm   52  1   Assignment1
Error   35  error MSB3721: The command "ml.exe /c /nologo /Zi /Fo"DebugAssignment1.obj" /W3 /errorReport:prompt  /TaAssignment1.asm" exited with code 1.   C:Program Files (x86)MSBuildMicrosoft.Cppv4.0BuildCustomizationsmasm.targets  49  6   Assignment1

Build x86 filament on windows 10 use vs2019,generated a lot of error in bluegl.prox #4780

Hello,I have to use filament on windows x86.
But I bulid it generated error like that.
E:WYfilamentfilament-mainlibsblueglsrcBlueGLCoreWindowsImpl.S(22): error A2013: .MODEL must precede this directive
1>E:WYfilamentfilament-mainlibsblueglsrcBlueGLCoreWindowsImpl.S(25): error A2034: must be in segment block : bluegl_glProgramUniform1dvEXT
1>E:WYfilamentfilament-mainlibsblueglsrcBlueGLCoreWindowsImpl.S(26): error A2034: must be in segment block
1>E:WYfilamentfilament-mainlibsblueglsrcBlueGLCoreWindowsImpl.S(27): error A2034: must be in segment block
1>E:WYfilamentfilament-mainlibsblueglsrcBlueGLCoreWindowsImpl.S(28): fatal error A1010: unmatched block nesting : bluegl_glProgramUniform1dvEXT
Is there any suggestions？I look forward to receiving your reply，thank u！

The text was updated successfully, but these errors were encountered:

Sorry but we can’t/won’t support x86 on Windows, only x86_64

@romainguy Is any version not supported anymore, including the previous version？

No we’ve never supported x86 on Windows, only on Android (and even there we plan on getting rid of it as soon as possible).

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

libffi ASM error(s) while building with MSVC 2013 #462

The text was updated successfully, but these errors were encountered:

Anyone tried to actually build with MSVC 2013, does it still work?

@Zueuk I have not, are you still getting an error if you use MSVC 2019 instead?

Everything is fine with 2017 and 2019

@nacho and @guruDanny67 maybe we should just drop support for MSVC 2013, and eventually add MSVC 2022. What do you think?

I thought there is something wrong with my VS2013 install, so I redownloaded & reinstalled it from the «VS Community 2013 with update 5» ISO.
Did not get asm errors after that, there were a bunch of C errors in libtiff and fontconfig, fixable by #define inline __inline and #define snprintf _snprintf , but then

All these lines have constexpr in there, and it seems to me that MSVC2013 even «with update 5» does not support it.

Perhaps there is a way to use an older version of this library with MSVC 2013?

@Zueuk Is there a reason why you need to build with a 9 year old version of MSVC? I am trying to figure out if there is a use case for this or we should drop support for these really old versions.

There was (is?) a remote possibility that our project will have to be built on MSVC 2013 for some legacy reasons.

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Вопрос По Асемблеру\

У меня в папке C:l11.asm лежит файл на асме код его
.386
.model flat.stdcall
.code
start:
mov eax. 2
add eax. 3
ret
end start

Я хочу превратить его в exe
Компилятор путь C:myasm
Я делаю 2 команды в cmd
C:myasmbinml.exe /c /coff C:l11.asm
C:myasmbinlink.exe /subsystem:windows C:l11.obj
Точнее пока 1 первую и выдаёт следующие

C:Documents and SettingsAdmin>C:myasmbinml.exe /c /coff C:l11.asm
Microsoft (R) Macro Assembler Version 6.14.8444
Copyright (C) Microsoft Corp 1981-1997. All rights reserved.

Assembling: C:l11.asm
C:l11.asm(2) : error A2008: syntax error : .
C:l11.asm(3) : error A2013: .MODEL must precede this directive
C:l11.asm(4) : error A2034: must be in segment block
C:l11.asm(5) : error A2008: syntax error : in instruction
C:l11.asm(6) : error A2008: syntax error : in instruction
C:l11.asm(7) : error A2034: must be in segment block
C:l11.asm(8) : error A2006: undefined symbol : start
C:l11.asm(8) : error A2148: invalid symbol type in expression : start

C:Documents and SettingsAdmin>

Что делать?( В чём ошибка?? У меня XP

.386
.model flat, stdcall
.code
start proc
mov eax, 2
add eax, 3
ret
start endp
end start

Нужно ставить запятые вместо точек. Возможно, блок исполняемого кода нужно оформить в виде процедуры.
И если не получится, попробуй между директивами .model и .code поставить option casemap: none

Источник

libffi ASM error(s) while building with MSVC 2013 #462

The text was updated successfully, but these errors were encountered:

Anyone tried to actually build with MSVC 2013, does it still work?

@Zueuk I have not, are you still getting an error if you use MSVC 2019 instead?

Everything is fine with 2017 and 2019

@nacho and @guruDanny67 maybe we should just drop support for MSVC 2013, and eventually add MSVC 2022. What do you think?

I thought there is something wrong with my VS2013 install, so I redownloaded & reinstalled it from the «VS Community 2013 with update 5» ISO.
Did not get asm errors after that, there were a bunch of C errors in libtiff and fontconfig, fixable by #define inline __inline and #define snprintf _snprintf , but then

All these lines have constexpr in there, and it seems to me that MSVC2013 even «with update 5» does not support it.

Perhaps there is a way to use an older version of this library with MSVC 2013?

@Zueuk Is there a reason why you need to build with a 9 year old version of MSVC? I am trying to figure out if there is a use case for this or we should drop support for these really old versions.

There was (is?) a remote possibility that our project will have to be built on MSVC 2013 for some legacy reasons.

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Error a2013 model must precede this directive

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

The following are different code fragments that are using .CODE and SEGMENT in the same listing and in some cases different results occur than the expected results. The name of all the listings are ASSEMBLY1.asm:

Case 1: no errors

.code ;segments created are PUBLIC and alignment is WORD

ASSEMBLY1_TEXT segment ;segments created are PUBLIC and alignment is WORD. This is because .code created the initial definition for ASSEMBLY1_TEXT segment to be PUBLIC and the alignment to be WORD

Case 2: Error occur, as it should

.code ASSEMBLY1_TEXT ;segments created are PUBLIC and alignment is WORD.

ASSEMBLY1_TEXT segment PRIVATE ;A error occurs here because the .CODE directive created this segment as PUBLIC and a alignment of WORD and now you are attempting to change the combine type from PUBLIC to PRIVATE.

CASE 3: NO error occurs BUG??

ASSEMBLY1_TEXT segment PRIVATE ;segments created are PRIVATE and alignment is PARA.

.code ;existing segment named ASSEMBLY1_TEXT that is PUBLIC and alignment of WORD. No error is shown. A error should occur because the combine type and alignments do not match.

Case 4: no error, BUG??

ASSEMBLY1_TEXT segment PRIVATE ;segments created are PRIVATE and alignment is PARA.

.code ; ;a segment named ASSEMBLY1_TEXT that was PRIVATE with a alignment of PARA is now changed to PUBLIC and alignment of WORD. No error is shown. A error should occur because the combine type and alignments do not match.

From the different testing of .CODE and SEGMENT I have determined when a .CODE directive is encountered ANY segments that are created by .CODE have a combine type of PUBLIC and a alignment of WORD. If a SEGMENT instruction is encountered and has no segment options defined then it creates a combine type of PRIVATE and an alignment of PARA.

I was expecting a .CODE directive to inherit the combine type and alignment where the original SEGEMENT instruction was first defined but that is not the case. Is this the way .CODE is suppose to work or is this a bug?

I was hoping to be able to define segments with options using the long form of SEGMENT and then use the .CODE and other directives. Does this not work?

I have not tried this yet for .DATA,.DATA. CONST,.FARDATA,.FARDATA? and .STACK. I expect the same result. Am I correct?

Thanks for any help, David

Well, masm/ml for Visual Studio 2017 doesn’t like the third case.

First you have ASSEMBLY1_TEXT as the start of the segment, but ASSEMBLY2_TEXT as the end of the segment, this results in the error:

Assembling: test.asm
test.asm(2) : fatal error A1010:unmatched block nesting : ASSEMBLY2_TEXT

since the blocks are unmatched. There is also the fact that you have ,code (comma) instead of .code.

Fixing that, so the assembly is:

Assembling: test.asm
test.asm(3) : error A2065:expected : memory model
test.asm(3) : error A2013:.MODEL must precede this directive
test.asm(4) : error A2013:.MODEL must precede this directive
test.asm(5) : error A2034:must be in segment block
test.asm(1) : error A2065:expected : memory model

because .model must have a memory model.

For case 4, the .model directive seems to retroactively affect all sections. So if it isn’t a section made with one of the macros (.code, .data etc.) then it doesn’t matter too much if it assumes something. Because the simple:

will change the alignment on its own, so for case 4, the alignment hasn’t been changed.

I think that for case 4, the retroactive applying of the memory model may also be affecting things. Before the memory model is set, _TEXT is not seen as a special section, so it would be seen as an initialised data section which isn’t executable. For example, if you don’t set the model, or explicitly set it to flat, the section properties are:

SECTION HEADER #3
/19 name (ASSEMBLY2_TEXT)
0 physical address
0 virtual address
0 size of raw data
0 file pointer to raw data
0 file pointer to relocation table
0 file pointer to line numbers
0 number of relocations
0 number of line numbers
C0500040 flags
Initialized Data
16 byte align
Read Write

This is obviously not what a .CODE section should be.

For it to match the memory model, the parameters must change to match code sections. So if you change the memory model after the fact, then it just treats it like that was the one defined right at the start. It is like how you can’t have multiple .model directives in the same file.

So it is possible that the assembler is just ignoring the private when the memory model is applied retroactively.

If you do believe this is a bug, then it is best to contact Microsoft using Visual Studio’s send feedback option, or on the developer community site.

This is a signature. Any samples given are not meant to have error checking or show best practices. They are meant to just illustrate a point. I may also give inefficient code or introduce some problems to discourage copy/paste coding. This is because the major point of my posts is to aid in the learning process.

Darran, sorry for the bad typing. Thanks for letting me know. I fixed Case 3 to the way it was suppose to be.

I was hoping that Microsoft would respond here without have to contact them.

The only way you can guarantee that a Microsoft employee will look at this is by contacting them. Employees from the various toolsets don’t come onto these forums very often.

Also, I’m not sure if case 3 is a problem at all. You can only define the memory model for an assembly file once, and the assembler doesn’t support changes in the memory model in the source file. If you try to do this, the assembler with warn you that it has found another .model directive and is ignoring it.

So even though the .model directive comes after the declaration of the segment, the segment cannot be declared with the default flat memory model because that would result with a change in the memory model.

So if you check the object after you assemble:

you will notice that the section properties are the same. So this is treating the .model that is declared after the initial section is influencing the section attributes:

SECTION HEADER #1
/19 name (ASSEMBLY2_TEXT)
0 physical address
0 virtual address
0 size of raw data
0 file pointer to raw data
0 file pointer to relocation table
0 file pointer to line numbers
0 number of relocations
0 number of line numbers
60220020 flags
Code
Purgeable
2 byte align
Execute Read

So while it does have different attributes compared to the default ones with the flat memory model (since this section isn’t special), the assembler treats the .model directive as if it came before all directives.

So the assembler seems to default to flat, and the first .model directive will affect the entire file.

This is also not that crazy when you think that to support the macros, the assembler has to do at least two phases. The directives and macros would be parsed on the first pass, and the rest of it would be parsed on the second pass. This is why you can define sections using segment/ends before the .model directive, but you can’t use .code before the .model directive.

This is a signature. Any samples given are not meant to have error checking or show best practices. They are meant to just illustrate a point. I may also give inefficient code or introduce some problems to discourage copy/paste coding. This is because the major point of my posts is to aid in the learning process.

Источник