Hi Tobias,
here's a gcc-4.5 patch which fixes: (1) the comment for fntype[2], (2) the
prototypes for the frexp family and (3) the prototypes for the scalbn family.
I checked all uses of all of the function types declared here and all the rest
seem to be correct. I also took a look at an example
Hi Ducan,
On 04/05/2011 11:41 AM, Duncan Sands wrote:
By the way I just noticed that the arguments to
the scalbn functions also seem to be the wrong way round:
here's a gcc-4.5 patch which fixes: (1) the comment for fntype[2], (2)
the
prototypes for the frexp family and (3) the prototypes for
Hi Tobias,
I do, so that's not a problem. By the way I just noticed that the arguments to
the scalbn functions also seem to be the wrong way round:
here's a gcc-4.5 patch which fixes: (1) the comment for fntype[2], (2) the
prototypes for the frexp family and (3) the prototypes for the scalbn f
Hi Tobias,
Pong. It helps to send Fortran patches also to fortran@ ...
indeed :)
On 30/03/11 16:43, Duncan Sands wrote:
While working on the dragonegg plugin I noticed that the Fortran front-end
declares frexp with the parameters the wrong way round. Instead of
double frexp(double x, int *e
Duncan Sands wrong:
Ping?
Pong. It helps to send Fortran patches also to fortran@ ...
On 30/03/11 16:43, Duncan Sands wrote:
While working on the dragonegg plugin I noticed that the Fortran
front-end
declares frexp with the parameters the wrong way round. Instead of
double frexp(double x, i
Ping?
On 30/03/11 16:43, Duncan Sands wrote:
While working on the dragonegg plugin I noticed that the Fortran front-end
declares frexp with the parameters the wrong way round. Instead of
double frexp(double x, int *exp);
it is declared as
double frexp(int *exp, double x);
This is fairly harmless
