On Monday, April 14, 2014 12:26:15 PM UTC+2, leif wrote: > > Jean-Pierre Flori wrote: > > FYI, same failure on gcc110 (linux/POWER7). > > g++ -v? > $ g++ -v Using built-in specs. COLLECT_GCC=/usr/bin/g++ COLLECT_LTO_WRAPPER=/usr/libexec/gcc/ppc64-redhat-linux/4.7.2/lto-wrapper Target: ppc64-redhat-linux Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --disable-build-with-cxx --disable-build-poststage1-with-cxx --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --with-linker-hash-style=gnu --enable-languages=c,c++,objc,obj-c++,java,fortran,ada,go,lto --enable-plugin --enable-initfini-array --enable-java-awt=gtk --disable-dssi --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-ppl --with-cloog --enable-secureplt --with-long-double-128 --build=ppc64-redhat-linux Thread model: posix gcc version 4.7.2 20121109 (Red Hat 4.7.2-8) (GCC)
> > The current "logic" in mpirxx.h is IMHO really pretty fragile. Note > btw. that C99 long longs aren't part of C++98, hence a preprocessor for > the latter (including '-std=c++98') doesn't even have to support them > (i.e., LL/ULL literals). > > Besides giving some macros more intuitive names, I'd first make sure > every used macro is indeed defined (and error out or give a warning > otherwise). (MPIR_HAVE_STDINT for example doesn't imply that it has > been included, nor that the relevant macros are defined [in C++].) > > I agree that prepending the tests for intmax_t != (long) long could be prepended with defined(...) && At least it would solve the PPL issue. -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to mpir-devel+unsubscr...@googlegroups.com. To post to this group, send email to mpir-devel@googlegroups.com. Visit this group at http://groups.google.com/group/mpir-devel. For more options, visit https://groups.google.com/d/optout.
