Fujitsu LLVM Fortran Bugs Status
Note: Fujitsu bugs reported upstream are now being tracked by LLVM project board in GitHub
Open Date | Status | Close Date | Upstream Bug ID | Notes from Fujitsu | Comments and Details (From Linaro) |
2022.11.14 | closed | 2023.1.27 | Fujitsu extension not to support |
| |
2022.11.14 | closed | 2023.1.27 | Fujitsu extension not to support |
| |
2022.11.14 | closed | 2023.1.27 |
| Fixed, verified and closed upstream. | |
2022.11.14 | open | - | Cray extension not to support | kkwli is working on it | |
2022.11.14 | closed | 2022.12.15 |
| Note a bug. Closed with comments upstream. | |
2022.11.14 | closed | 2022.12.15 |
| Fixed, verified and closed upstream. | |
2022.11.21 | closed | 2022.11.22 | OK with latest version |
| |
2022.11.21 | closed | 2022.11.22 | OK with latest version |
| |
2022.12.05 | closed | 2023.1.27 | Abort at 'where' in forall construct | Closed with fix to emit “not yet implemented: substring of static object inside FORALL” | |
2023.01.23 | closed | 2023.2.14 | Mix with user-define and intrinsic 'sign' functions | Ihttps://linaro.atlassian.net/browse/LLVM-856 Invalid, not allowed by the standard | |
2023.01.23 | open | - | generic interface | https://linaro.atlassian.net/browse/LLVM-857 Besides allowing interfaces using functions with the same name in Semantics, a new mechanism must be implemented to handle this | |
2023.01.23 | In- Progress | 2023.4.6 | allocatable attriburte | https://linaro.atlassian.net/browse/LLVM-858 Attributes of function call return value are not being preserved. It either needs to be obtained by going over the expression elements or this attribute must be saved in the type characteristics. | |
2023.01.23 | Fixed | 2023.3.6 | Error on ommiting actual argument | flang is not handling omission of optional function argument properly. fir.absent probably has to be extended | |
2023.01.23 | open | - | Too long compile time | Compilation finishes after ~3mins, using over 60GB of RAM. ~70% of the time is spent converting MLIR to LLVMIR. Seems to be a scalability issue. | |
2023.01.23 | closed | 2023.2.13 | Error on derived type | Leandro Fixed it by: | |
2023.01.23 | open | - | Dummy argument attribute | shourya5 wants to take this and s-pratik also wants to contribute | |
2023.01.23 | closed | 2023.2.14 | attribute of arguments in allocate statement | Fixed by: | |
2023.01.23 | closed | 2023.3.31 | Segmentation fault | ANY works with arrays of the same rank, directly or after linearization ((//)). Some property from the array before linearization is probably being used, incorrectly | |
2023.02.06 | closed |
|
|
| |
2023.02.06 | closed |
|
| Closed duplicate of #60223 |