> There is now only one out of order declaration in the repository code as > follows: > > ode-initval2\test.c (2185 ...) out of order declarations: > ------------------------------------ /* Test driver_apply_fixed_step */ > > gsl_odeiv2_driver_reset_hstart (d, 1e-3); > const unsigned long int nfsteps = 100000; > const double hfixed = 0.000025; > s = gsl_odeiv2_driver_apply_fixed_step (d, &t, hfixed, nfsteps, y); > > if (s != GSL_SUCCESS) > ------------------------------------
Please consider dropping this into a bug report at https://savannah.gnu.org/projects/gsl/ > There are, however, quite a few test errors as follows: > > ... > > I would be most grateful to know which of these are 'work in progress' and > which are unexpected and might hence be specific to a Visual Studio GSL > build. How many of the errors you report persist when you compile in debug mode (i.e. -O0)? I am aware of test tolerances being problematic on Intel compilers at -O2 or -O3. I suspect Microsoft compilers will similarly perturb the numerical results when optimization is enabled. Anything that breaks at -O0 is certainly suspect. - Rhys
