summaryrefslogtreecommitdiffstats
path: root/Source/LexerParser/cmFortranParser.y
Commit message (Collapse)AuthorAgeFilesLines
* Fortran: Fix suprious dependencies with submodulesVitaly Mogulian2022-08-091-11/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | In commit 695f0d0d3a (cmFortranParser: Parse keywords as lexical tokens, 2016-09-05, v3.7.0-rc1~150^2) we created keyword-specific variants of the original `USE WORD other EOSTMT` production, such as `MODULE WORD other EOSTMT` and `INTERFACE WORD other EOSTMT`. The same pattern was used by more keyword-specific productions in commit b5ac8b8aa7 (Fortran: Add support for submodule syntax in dependency scanning, 2016-09-05, v3.7.0-rc1~73^2~1). The postfix part (`other`) of several keyword-specific productions is not needed to match Fortran syntax. See the Fortran 2018 standard, para.4.1.4/1 on p.28, para.14.2.1/2 on pp.293-294. The postfix is needed only for a case of operator 'use': use <module-name> [, only : <list-of-vars>] The unnecessary postfix matching from the keyword-specific productions such as module, submodule, and interface declarations can cause spurious module dependencies to be detected, so remove it. Extend the test suite with examples covering the previously-broken cases. Fixes: #18427
* LexerParser: Suppress clang -Wunused-but-set-variable warningsBrad King2022-04-061-0/+5
|
* Makefiles: Add support for building Fortran intrinsicsIsuru Fernando2021-06-241-0/+4
| | | | Fixes: #21463
* LexerParser: Do not leak Fortran parser tokens discarded due to errorsBrad King2021-06-081-0/+2
|
* LexerParser: Suppress gcc -Wfree-nonheap-object warnings in generated codeBrad King2021-02-051-0/+1
|
* LexerParser: Clean up includes following include-what-you-useChristoph Grüninger2021-01-251-1/+0
|
* LexerParser: Manual removing code from Bison is no longer neededChristoph Grüninger2021-01-251-2/+0
| | | | | This was needed to avoid warnings while compiling the sources generated by older versions of GNU Bison, but is not with GNU Bison 3.7.4.
* LexerParser: Do not use GNU Bison's yacc mode, we use Bison extensionsChristoph Grüninger2021-01-251-1/+1
| | | | Silence Bison warnings regarding use of Bison extensions.
* Fortran: ignore CPP line directives in line-continued USE stmtsTiziano Müller2019-11-131-0/+1
| | | | Issue: #18188
* LexerParser: Suppress GCC -Wconversion warningsBrad King2018-07-311-0/+3
| | | | | GCC 8 warns about some of the conversions in bison-generated code. Suppress the warnings.
* Fortran: Add support for submodule dependenciesBrad King2018-04-201-2/+2
| | | | | | | | | | | | | | | | | | | | | Since commit v3.7.0-rc1~73^2~1 (Fortran: Add support for submodule syntax in dependency scanning, 2016-09-05) we support parsing Fortran sources that use submodule syntax, but it left addition of `.smod` dependencies to future work. Add it now. The syntax submodule (module_name) submodule_name means the current source requires `module_name.mod` and provides `module_name@submodule_name.smod`. The syntax submodule (module_name:submodule_name) nested_submodule_name means the current source requires `module_name@submodule_name.smod` provides `module_name@nested_submodule_name.smod`. Fixes: #17017
* LexerParser: move to custom directoryDaniel Pfeifer2017-04-281-0/+247
generated by cgit v0.12 at 2025-02-03 18:36:22 (GMT)