On 12/18/23 16:41, Jisca Huisman wrote:
Hello Ivan & Tomas,
Thank you for your time and helpful suggestions!
The finer details of memory use and heap vs stack are still outside my
comfort zone, but some trial and error shows that using an allocatable
does indeed solve the issue. When using
Hello Ivan & Tomas,
Thank you for your time and helpful suggestions!
The finer details of memory use and heap vs stack are still outside my
comfort zone, but some trial and error shows that using an allocatable
does indeed solve the issue. When using the largest value I expect users
to use
On 12/18/23 15:09, Ivan Krylov wrote:
В Mon, 18 Dec 2023 11:06:16 +0100
Jisca Huisman пишет:
I isolated the problem in a minimal working example available here:
https://github.com/JiscaH/flang_segfault_min_example . All that does
is pass a vector of length N*N back and forth between R and
В Mon, 18 Dec 2023 11:06:16 +0100
Jisca Huisman пишет:
> I isolated the problem in a minimal working example available here:
> https://github.com/JiscaH/flang_segfault_min_example . All that does
> is pass a vector of length N*N back and forth between R and Fortran.
> It works fine for very
Hello,
My package sequoia contains Fortran code, and failed to pass the
pre-test on Debian with the new flang-new compiler. I was able to
reproduce the issue, but strongly suspect it is an issue with
flang-new-17 rather than with my code. However, since in the past when I
thought the problem
On Sun, 17 Dec 2023 21:48:51 +0200
Christiaan Pieterse wrote:
> Warning in complexity_measures(Mbin, method = "reflections",
> iterations = iterCompl) :
> 'iterations' was changed to 'iterations + 1' to work with an even
> number of iterations
> Killed
If this is happening on Linux, this
