GMP is now deeply integrated into Maple - which I consider to be a good thing.  But it appears that compiler writers are doing a bad job (see the first paragraph on GMP's home page)  In other words, unless you carefully make sure that you have compile GMP properly, it is entirely possible that you end up with a buggy library.  Very scary stuff.

Hopefully Maplesoft runs 'make check' (and looks at the results carefully!) before bundling in GMP.  Suggestion: why not bundle the output of 'make check' in with GMP?  [Either beside the library object file, or beside the license text file].  This would greatly increase the confidence of the users (most importantly, of the users using Maple for engineering tasks) that crucial parts of Maple are properly built.  In some ways, this can be a marketing advantage: Maplesoft is willing to be more transparent than its competitors on the correctness of its low-level core routines.

Of course, the scary part is that some compilers manage to break GMP at all.  Hopefully, compiling GMP (and its test suite, naturally) will become part of the standard test suite of all compilers!