Visual studio 2019 do not want to produce ASM files for LIB release, what I'm doing wrong?

Question

0.00/5 (No votes)

See more:

VS2019

I'm using this command line:

/permissive- /MP /GS- /Qpar /GL /W4 /wd"4530" /Gy /Zc:wchar_t /I"C:\oTemplates\oLib\oLib\src" /I"C:\oTemplates\oLib\oLib\inc" /Gm- /Ox /Fd"C:\oTemplates\oLib\oLib\tmp\64aRavx2\vc142" /fp:precise /Zp1 /D "AMD" /D "NDEBUG" /D "_CONSOLE" /fp:except- /errorReport:none /GF- /WX- /Zc:forScope /GR- /arch:AVX2 /Gv /Oi /MD /FC /Fa"C:\oTemplates\oLib\oLib\asm\64aRavx2\" /nologo /Fo"C:\oTemplates\oLib\oLib\tmp\64aRavx2\" /FAcs /Ot /diagnostics:column /Ob3 /favor:AMD64

to compile LIB project in VS 2019 and

"C:\oTemplates\oLib\oLib\asm\64aRavx2\"

stays empty. But it's being created during compile time.

If I switch to Debug settings:

/JMC /permissive- /MP /GS- /W4 /wd"4530" /Zc:wchar_t /I"C:\oTemplates\oLib\oLib\src" /I"C:\oTemplates\oLib\oLib\inc" /ZI /Gm- /Od /Fd"C:\oTemplates\oLib\oLib\tmp\64aDavx2\vc142" /fp:precise /Zp1 /D "AMD" /D "_DEBUG" /D "_CONSOLE" /fp:except- /errorReport:none /GF- /WX- /Zc:forScope /RTC1 /GR- /arch:AVX2 /Gv /MDd /FC /Fa"C:\oTemplates\oLib\oLib\asm\64aDavx2\" /nologo /Fo"C:\oTemplates\oLib\oLib\tmp\64aDavx2\" /FAcs /diagnostics:column /Ob3 /favor:AMD64

or, if I'm switching project type from LIB to EXE, correspondig folder being filled with ".asm" files as usual.
Compiler won't generate asm files only for Static Library Release versions of the same code.

What I'm doing wrong or how to determine what's the problem is in?

What I have tried:

BTW, output produces no errors in any of the ways:

1>------ Rebuild All started: Project: oLib, Configuration: Release - AVX2 64 AMD ------
1>lib.cpp
1>oLib.vcxproj -> C:\oTemplates\oLib\oLib\bin\oLib64aRavx2.lib
========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==========

Posted 28-Nov-19 0:20am

Ovodus

Updated 30-Nov-19 3:28am

v2

Add a Solution

3 solutions

Solution 1

I've seen recently a note saying that MSVC compiler does not support inline assembly for x86 64-bits CPU family.
This was in a project called angelscript.
Angelscript - Copile the library - Considerations for specific platforms[^]
For 64-bits builds, there is a pre-build event setup which takes care of inline assembly generation. Maybe you can study how they solved this issue?

Posted 28-Nov-19 0:51am

phil.o

Comments

Ovodus 28-Nov-19 7:12am

It's not about it. It's about any project's:
"Configuration Properties"->"C/C++"->"Output Files"->"Assembler Output" & "Configuration Properties"->"C/C++"->"Output Files"->"ASM List Location".
Hope it's more clear now. It's a good feature, which helps to understand the way the compiler works with your code.

BTW: "Assembler Inlining" is not supported, indeed. But no one denies you to use MASM in your project. Long story short, it's required now to keep asm code in separated files.

Solution 2

Create a DLL project and in Visual Studio, add all the existing files from the static Lib project to DLL project. Make sure you do not copy the source files to DLL project folder to avoid source code duplication: The DLL project can access the source files from static Lib project folder just fine.

Build the DLL with asm generation. There you have your assembly code.

Posted 28-Nov-19 13:27pm

Shao Voon Wong

Comments

Ovodus 30-Nov-19 9:36am

Unfortunately, it's not an option for me. I need to build an automated compilation system to benchmark different algorithms under different CPUs in lots of different conditions. Manual project modifications will cost me tons of time and will make my reports invalid due to probable mistakes.

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Ovodus · Accepted Answer · 2019-11-30T03:28:00

Solution 3

For LIB projects, it's required to remove /GL option ("Configuration Properties"->"C/C++"->"Optimization"->"Whole Program Optimization") to produce .asm files.

Posted 30-Nov-19 3:28am

Ovodus