This is the mail archive of the gcc@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] | |
32-bit integers are going to remain useful types, and LP64 architectures finally have char = 8, short = 16, int = 32, long = 64, which is too useful to break.
"Handle and Pointer Sizes" in http://www.intel.com/cd/ids/developer/asmo-na/eng/dc/64bit/197664.htm?page=2
When I try to attach the qualification "useful" to program text whose basic types cannot be interpreted without extended exegesis of various documents, I wonder whether it should be the compiler's job to correct this situation, as has been suggested in this thread.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |