GNU bug report logs - #36036
Visual Studio 2019 compiler errors not detected/recognized by compile.el

Previous Next

To reply to this bug, email your comments to 36036 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Bret Needle <Bret_Needle <at> Yahoo.com>
To: bug-gnu-emacs <at> gnu.org
Subject: Visual Studio 2019 compiler errors not detected/recognized by
 compile.el
Date: Fri, 31 May 2019 14:00:24 -0700

Configuration:

?????? GNU Emacs 26.2 (build 1, x86_64-w64-mingw32) of 2019-04-13

?????? Microsoft Visual Studio 2019 (Community Edition)

Bug Behavior:

The default setting of the diagnostic mode option 
(/diagnostic:classic|column|caret) is now column when creating new C++ 
(VC) projects with VS 2019.?? This mode produces compiler error messages 
in the following format:

File name(line number, column number): error message ...

This new format is not recognized by the Microsoft (msft) regular 
expression check in compile.el.

Thanks,

Bret Needle (Bret_Needle <at> Yahoo.com)

Message #10 received at 36036 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Bret Needle <Bret_Needle <at> Yahoo.com>
Cc: 36036 <at> debbugs.gnu.org
Subject: Re: bug#36036: Visual Studio 2019 compiler errors not
 detected/recognized by compile.el
Date: Thu, 10 Oct 2019 01:22:17 +0200

Bret Needle <Bret_Needle <at> Yahoo.com> writes:

> The default setting of the diagnostic mode option
> (/diagnostic:classic|column|caret) is now column when creating new C++ 
> (VC) projects with VS 2019.?? This mode produces compiler error
> messages in the following format:
>
> File name(line number, column number): error message ...
>
> This new format is not recognized by the Microsoft (msft) regular
> expression check in compile.el.

Do you have some actual sample output from this compiler?  That will
make it easier to check whether a fix actually works.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Message #15 received at 36036 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: 36036 <at> debbugs.gnu.org
Subject: [Bret Needle] Re: bug#36036: Visual Studio 2019 compiler errors not
 detected/recognized by compile.el
Date: Mon, 14 Oct 2019 23:41:36 +0200

-------------------- Start of forwarded message --------------------
Subject: Re: bug#36036: Visual Studio 2019 compiler errors not
 detected/recognized by compile.el
To: Lars Ingebrigtsen <larsi <at> gnus.org>
From: Bret Needle <Bret_Needle <at> Yahoo.com>
Date: Sat, 12 Oct 2019 17:58:45 -0700

Hello Lars Ingebrigtsen.

Thanks for your follow-up and sorry for the omission.  This message 
occurs when I compile with the diagnostics setting set to "classic":

ClCompile:
   C:\Program Files (x86)\Microsoft Visual 
Studio\2019\Community\VC\Tools\MSVC\14.22.27905\bin\HostX86\x64\CL.exe 
/c /ZI /JMC /nologo /W3 /WX- /diagnostics:classic /sdl /Od /D _DEBUG /D 
_CONSOLE /D _UNICODE /D UNICODE /Gm- /EHsc /RTC1 /MDd /GS /fp:precise 
/Qspectre /permissive- /Zc:wchar_t /Zc:forScope /Zc:inline /std:c++17 
/Fo"x64\Debug\\" /Fd"x64\Debug\vc142.pdb" /Gd /TP /FC /errorReport:queue 
Lesson08.cpp
   Lesson08.cpp
c:\Users\Bret\Documents\Visual Studio 
2019\Projects\Lesson08\Lesson08\Lesson08.cpp(9): error C3861: 'bogus': 
identifier not found [c:\Users\Bret\Documents\Visual Studio 
2019\Projects\Lesson08\Lesson08\Lesson08.vcxproj]
Done Building Project "c:\Users\Bret\Documents\Visual Studio 
2019\Projects\Lesson08\Lesson08\Lesson08.vcxproj" (Rebuild target(s)) -- 
FAILED.
Done Building Project "c:\Users\Bret\Documents\Visual Studio 
2019\Projects\Lesson08\Lesson08.sln" (rebuild target(s)) -- FAILED.

This message occurs when I compile with the diagnostics setting set to 
"column":

ClCompile:
   C:\Program Files (x86)\Microsoft Visual 
Studio\2019\Community\VC\Tools\MSVC\14.22.27905\bin\HostX86\x64\CL.exe 
/c /ZI /JMC /nologo /W3 /WX- /diagnostics:column /sdl /Od /D _DEBUG /D 
_CONSOLE /D _UNICODE /D UNICODE /Gm- /EHsc /RTC1 /MDd /GS /fp:precise 
/Qspectre /permissive- /Zc:wchar_t /Zc:forScope /Zc:inline /std:c++17 
/Fo"x64\Debug\\" /Fd"x64\Debug\vc142.pdb" /Gd /TP /FC /errorReport:queue 
Lesson08.cpp
   Lesson08.cpp
c:\Users\Bret\Documents\Visual Studio 
2019\Projects\Lesson08\Lesson08\Lesson08.cpp(9,4): error C3861: 'bogus': 
identifier not found [c:\Users\Bret\Documents\Visual Studio 
2019\Projects\Lesson08\Lesson08\Lesson08.vcxproj]
Done Building Project "c:\Users\Bret\Documents\Visual Studio 
2019\Projects\Lesson08\Lesson08\Lesson08.vcxproj" (Rebuild target(s)) -- 
FAILED.
Done Building Project "c:\Users\Bret\Documents\Visual Studio 
2019\Projects\Lesson08\Lesson08.sln" (rebuild target(s)) -- FAILED.

I encourage you or the bug fixer to implement search patterns that 
successfully recognize both messages.

Regards, Bret Needle

On 10/9/2019 4:22 PM, Lars Ingebrigtsen wrote:
> Bret Needle <Bret_Needle <at> Yahoo.com> writes:
>
>> The default setting of the diagnostic mode option
>> (/diagnostic:classic|column|caret) is now column when creating new C++
>> (VC) projects with VS 2019.?? This mode produces compiler error
>> messages in the following format:
>>
>> File name(line number, column number): error message ...
>>
>> This new format is not recognized by the Microsoft (msft) regular
>> expression check in compile.el.
> Do you have some actual sample output from this compiler?  That will
> make it easier to check whether a fix actually works.
>

-------------------- End of forwarded message --------------------

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.