This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 09/04/2009 02:52 PM, Kai Tietz wrote:Well, I bootstrapped this with Paolo's stdint.m4 patch, and it workedon linux32 and linux64 (i386), and for x86_64-pc-mingw32, too. Just out of curiosity, who is the size in gfortran frontend for int_{least,fast}*_t done, as for gcc until now no stdint.h/inttypes.h file was used?
Actually, I do not know how exactly it works ... I now checked - and here is how it works:
In gcc/fortran/ one calls: TYPE_PRECISION (type) for INT_FAST64_TYPE etc. The defaults are set in gcc/default.h
For instance: #ifndef INT_FAST64_TYPE #define INT_FAST64_TYPE ((const char *) NULL) #endif
And the INT_*_TYPE definitions can seemingly found in config/*/*stdint.h. For instance: ./i386/cygwin-stdint.h:#define INT_FAST64_TYPE "long long int" ./i386/mingw-stdint.h:#define INT_FAST64_TYPE "long long int" ./glibc-stdint.h:#define INT_FAST64_TYPE (LONG_TYPE_SIZE == 64 ? "long int" : "long long int")
Thus, stdint.h is not directly involved and the patch should have no (adverse) effect on gfortran's c_int_fast*_t support.
Attachment:
stdint.m4
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |