Albert Ziegenhagel

This file should be generated during the build process automatically but you need to have the Windows Driver Kit (WDK) installed. In #48 you can find the link to a...

I've just opened a pull request at flang-compiler/clang#37 that applies additional changes to the compiler driver. These changes add additional linker arguments so that the correct runtime libraries are linked....

It was a missing `__declspec(dllexport)` again. WINDOWS_EXPORT_ALL_SYMBOLS solved that. Now the executable links successfully but does not produce any output when being executed. I will dig deeper into that!

I can reproduce the same behavior when linking to the static flang runtime.

> My understanding is it calls into [`vsdbg.exe`](https://github.com/microsoft/vscode-cpptools/blob/ce2fcf0c62abc808d1485452d5720506762c42f2/Extension/src/Debugger/debugAdapterDescriptorFactory.ts#L53-L54) which is the VS Debugger. But I don't see Visual Studio ever call into this binary when debugging, so is vsdbg specifically...

I have pushed the code for the "Concord" extension to https://github.com/albertziegenhagel/childdebugger-concord and the regular VS Code extension that is supposed to work together with the Concord extension can be found...

The language type was already set to `FreeFormFortran`. But even if I rename the file to `include.f90` the error still exists (although in that case I do additionally get the...

I would say the issue is that in [compilers.ts#L144-L163](https://github.com/fortran-lang/vscode-fortran-support/blob/b35cbf5732102e54dc9a8b01a3853a10f11727d2/src/lint/compilers.ts#L144-L163) the `fname` from the match is simply ignored and then in [provider.ts#L329-L350](https://github.com/fortran-lang/vscode-fortran-support/blob/b35cbf5732102e54dc9a8b01a3853a10f11727d2/src/lint/provider.ts#L329-L350) all errors are reported in `document.uri`, which is the...

Yes, I can confirm that this is still an issue (checked version `v3.4.2024041503`).

I have added a changelog entry for this under "Changed". Let me know if you would rather consider this a "fix" (or anything else) and I will adjust it accordingly....