This is the mail archive of the libc-hacker@sourceware.cygnus.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Hi! Is it really necessary to specify the above two things in size_t as opposed to int32_t? It looks to me like the file formats carefully use 32bit types for most of the things (plus obviously strings, wide strings and byte sequences), but the above are two only thing which differ between sparc32 and sparc64 locale files. Especially it does not make much sense to me when ld-collate.c does nothing to make sure those size_t numbers are actually aligned to its size in the file (often they are not, just 32bit aligned while size_t can be 64bit). I'd be very happy if this could be sorted out, so that /usr/lib/locale/ can be shared between sparc 32bit and 64bit libraries. Those files are obviously endian dependant, but it would be great if they were not also wordsize dependant. Cheers, Jakub ___________________________________________________________________ Jakub Jelinek | jakub@redhat.com | http://sunsite.mff.cuni.cz/~jj Linux version 2.3.41 on a sparc64 machine (1343.49 BogoMips) ___________________________________________________________________
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |