mecej4g

I am able to reproduce these warning messages from the programs on a Linux box with the Intel compiler when I use certain optimization options. PC: Beelink micro-pc, AMD 4700U...

Which is the test case that went into an apparent infinite loop? I'd like to explore it further. Is it one of the examples in the `test` directory?

I am so far unable to reproduce the problem with LSODAR. If you don't mind, please see if changing the INTENT of the argument DY of DCOPY to (IN OUT)...

Here is what goes wrong. The function `dumach()` is called to obtain the machine epsilon. With **-fast**, the code returns zero instead of epsilon. The original code of dumach() contains...

Yes, with ifort /O2 on Windows the "Poor iterative algorithm performance seen" warnings come up for the LSODPK example. They go away if I add /fp:precise. Before I made the...

I am reopening this issue (which I had earlier closed) since I have found that there is something unusual in either the code or the algorithm itself that causes these...

I am not an FPM user, so I can only tell you the flags that I used with the NAG compiler, starting in the `src` directory: ``` nagfor -dusty -C...

Once the bugs have been removed, the NAG compiler can be used with no option flags needed other than `-dusty`. Furthermore, if the user is not hunting for bugs, the...