Hi Jeff, > > I have attempted to bugreport GCC here: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116885 > > Maybe Off-topic, or maybe related... Your bug report said the code has > worked fine for the last 20 years or so. Vararg changed recently. For > example, va_start now takes two arguments. You should have gotten a > compiler warning like '#error "GCC no longer implements <varargs.h>."' > You should include <stdarg.h> and make the changes as described in > <https://stackoverflow.com/q/24950362>. This is 7 years old ;).
Anyway, I recall that even Borland C++ for DOS from 1989 required 2 arguments. May be that it accepted both variants. So this "recent" change become at least before 30 years ;). I have implemented unittest and it will catch possible problems. ------------------------------------------------------------------ The recent change in GCC seems that it is no longer possible to pickup const double e = va_arg(ap,uint64_t) even when type size matches. May be that doubles are no longer stored on a stack, but in AVX registry. I do not know any other compiller that does something like this. const double e = va_arg(ap,double) thanks Jara _______________________________________________ cfarm-users mailing list cfarm-users@lists.tetaneutral.net https://lists.tetaneutral.net/listinfo/cfarm-users
