flang

flang copied to clipboard

minloc/maxloc output wrong results

2

```fortran program t1 integer square(3,6) integer res(3) square(1,:) = (/1,18,4,15,7,12/) square(2,:) = (/2,17,5,14,8,11/) square(3,:) = (/3,16,6,13,9,10/) res = minloc(square(1:3,4:6),dim=1) print *, res end output: 0 0 0 expect: 3 3...

erjin

Fix a min-max bug

1

This patch solves two problems: 1. According to the fortran 2008 standard, add syntax check for MAX/MIN intrinsic, as follows: > The arguments shall all be of the same type...

Liuyunlong0336

[from discourse] Wrong understanding of the rules for lbound and ubound for non-pointer dummy arguments

7

This issue was signaled on discourse as such: https://fortran-lang.discourse.group/t/an-interesting-difference-between-compilers/7131 There is also a reproducer initially written for AOCC, but since AOCC is based on classic flang, it can also be...

pawosm-arm

When the compiler's frontend is generating a piece of IR for `alloc04` call to the Fortran runtime library, for the polymorphic data type the `len` parameter is always 0 (namely,...

pawosm-arm

consider following code: ``` program string_init print *, fun(128) contains character(n) function fun(n) if (n .gt. 0) then fun = '?' else fun = '' end if end function end...

pawosm-arm

521.wrf_r segfaults when built with -flto=full -O2

17

After upgrading to LLVM 17, the 521.wrf_r benchmark in SPEC CPU2017 is miscompiled at O3 with LTO enabled. Examination of the crash site shows that a large amount of code...

bryanpkc

Emphasize && operator precedence with extra brackets, as suggested by clang warning

2

Emphasize && operator precedence with extra brackets, as suggested by clang warning

dmikushin

Adding intent(in)

3

Planting intent(in) all over the code, per strict modern Fortran compilers requirements. Do not duplicate eq and == , ne and /= operators definitions, as they seem to be already...

dmikushin

Do not dump debug location if debug info is not available

4

This works around the crash due to the NULL value of `module->debug_info`.

dmikushin

gdb.fortran testsuite : logical .TRUE. value printing is not correct

2

Affects a few tests like logical.exp in gdb.fortran testsuite. program mn logical :: x = .TRUE. logical :: y = .FALSE. print *, x print *, y end program (gdb)...

kiranchandramohan