Annoying ".i90",".i" files when using ifort compiler

gnikit · November 12, 2022, 7:12am

I think the combo of the mandatory linter flags for ifort might be causing the .i90 files to persist, see:

fortran-lang/vscode-fortran-support/blob/e0594034190bf7e6c85711e974cbc3c84127ff03/src/lib/linters.ts#L164


      
          constructor() {
            super(
              'ifort',
              /^(?<fname>(?:\w:\\)?.*)\((?<ln>\d+)\):\s*(?:#(?:(?<sev2>\w*):\s*(?<msg2>.*$))|(?<sev1>\w*)\s*(?<msg1>.*$)(?:\s*.*\s*)(?<cn>-*\^))/gm,
              {
                errors: ['error', 'fatal error'],
                warnings: ['warning', 'remark'],
                infos: ['info', 'note'],
                hints: ['hint'],
              },
              ['-syntax-only', '-fpp'],
              ['-warn', 'all'],
              '-module'
            );
          }
          /**
           * see https://regex101.com/r/GZ0Lzz/2
           * @param msg linter output
           * @returns array of vscode.Diagnostic
           */
          public parse(msg: string): vscode.Diagnostic[] {

would you recommend using some other combo of flags? Maybe include -no-save-temps?

Topic		Replies	Views
Anybody out there using VS Code + Modern Fortran extension + Ifort/Ifx on Windows? Help	3	1834	August 25, 2022
Intel fortran to gfortran Help	8	1016	June 12, 2022
Specifying fortran 77 vs fortran 90 in vscode fortran server Visual Studio Code	9	310	March 11, 2024
Help regarding the linter while developing fpm Help	1	292	July 4, 2022
Issues with Intel Fortran in Visual Studio	25	5158	September 6, 2022

Annoying ".i90",".i" files when using ifort compiler

Related Topics