Extra colon in compiler output confuses visual studio error list

[Tymek1200]

Suppose I make a mistake, that intellisense can't see.

The compiler throws an error.

Unfortunately said error misses a source file (Plik) and has an invalid line (W...). Which forces me to manually search the output window.

Here, we can see an extra colon which trips up visual studio. I've confirmed that's the issue by echoing the same error with and without the extra colon. Also I've commented out the orginal source of error so it wouldn't interfere with results.

With extra colon (interestingly no error):

Without extra colon (file and line works as intended):

That was a simple example, but in larger projects with warnings this is not a pleasant experience.

Tested on Visual Studio Community 2022 17.13.6 and Intel oneAPI C++ Compiler 2025.1.0

[Viet_H_Intel]

For "error: call to undeclared function 'someFunction'; ISO C99 and later do not support implicit function declarations", you need to have function prototype declaration or compile with -Wno-implicit-function-declaration

[yzh_intel]

Hi, I reproduced your issue, but I suspect the issue is from Visual studio, could you try to compile the code in command line ? I couldn't see the extra colon in the screen output. I'm using Microsoft Visual Studio Enterprise 2022 (64-bit) - Version 17.14.2 and Intel® C++ Compiler 2025.1.

[Tymek1200]

Hello. I had tried to run msbuild and got an error with extra colon present.

msbuild /p:Configuration="TEST"

Then I tried to compile the program with the logged command and (surprisingly) the extra colon is not present.

When I set up a pre build event (the same I used to echo fake error) to run icx prematurely the extra colon is still not present.

That probably means the ClCompile is to blame, but that is just a theory.

Also as a control test I recompiled the project from Visual Studio and the extra colon is still here.

[yzh_intel]

Hi @Tymek1200 , the issue was in the integration of Intel oneapi dpc++/c++ compiler with visual studio. It has been fixed in the latest oneapi toolkit. I can see the fix on my end and the error list now shows the correct information. Could you try the latest release 2025.3 ?