Re: [PATCH] Fortran: handle explicit-shape specs with constant bounds [PR105954]

Hello Harald, after simplification of constant bound expressions of an explicit shape spec of an array, we need to ensure that we never obtain negative extents. In some cases this did happen, and we ICEd as we hit an assert that this should never happen... The original testcase by Gerhard exhi

Re: [PATCH] Fortran: fix simplification of INDEX(str1,str2) [PR105691]

Hello Harald, compile time simplification of INDEX(str1,str2,back=.true.) gave wrong results. Looking at gfc_simplify_index, this appeared to be close to a complete mess, while the runtime library code - which was developed later - was a relief. The solution is to use the runtime library code

Re: [PATCH] fortran, libgfortran, v2: Avoid using libquadmath for glibc 2.26+

Hello, I don’t like the _Float128 vs __float128 business, it’s confusing. And accordinog to https://gcc.gnu.org/onlinedocs/gcc/Floating-Types.html they seem to be basically the same thing, so it’s also redundant. Is there a reason why the standard one, _Float128, can’t be used everywhere? Mikae

Re: [PATCH] Fortran: fix simplification of INDEX(str1,str2) [PR105691]

Hi Thomas, thanks for the reviews! Harald Am 26.06.22 um 11:14 schrieb Thomas Koenig via Fortran: Hello Harald, compile time simplification of INDEX(str1,str2,back=.true.) gave wrong results.  Looking at gfc_simplify_index, this appeared to be close to a complete mess, while the runtime libr

[PATCH v2 4/7] fortran: use grep instead of fgrep

fgrep has been deprecated in favor of grep -F for a long time, and the next grep release (3.8 or 4.0) will print a warning of fgrep is used. Stop using fgrep so we won't see the warning. We can't hard code grep -F here or it may break build on hosts w/o GNU grep. autoconf documentation contains a