What’s sizeof(size_t) on 32-bit vs the various 64-bit data models?

by

size_t is defined by the C standard to be the unsigned integer return type of the sizeof operator (C99 6.3.5.4.4), and the argument of malloc and friends (C99 7.20.3.3 etc). The actual range is set such that the maximum (SIZE_MAX) is at least 65535 (C99 7.18.3.2).

However, this doesn’t let us determine sizeof(size_t). The implementation is free to use any representation it likes for size_t – so there is no upper bound on size – and the implementation is also free to define a byte as 16-bits, in which case size_t can be equivalent to unsigned char.

Putting that aside, however, in general you’ll have 32-bit size_t on 32-bit programs, and 64-bit on 64-bit programs, regardless of the data model. Generally the data model only affects static data; for example, in GCC:

`-mcmodel=small'
     Generate code for the small code model: the program and its
     symbols must be linked in the lower 2 GB of the address space.
     Pointers are 64 bits.  Programs can be statically or dynamically
     linked.  This is the default code model.

`-mcmodel=kernel'
     Generate code for the kernel code model.  The kernel runs in the
     negative 2 GB of the address space.  This model has to be used for
     Linux kernel code.

`-mcmodel=medium'
     Generate code for the medium model: The program is linked in the
     lower 2 GB of the address space but symbols can be located
     anywhere in the address space.  Programs can be statically or
     dynamically linked, but building of shared libraries are not
     supported with the medium model.

`-mcmodel=large'
     Generate code for the large model: This model makes no assumptions
     about addresses and sizes of sections.

You’ll note that pointers are 64-bit in all cases; and there’s little point to having 64-bit pointers but not 64-bit sizes, after all.

More Related Contents:

  1. What decides the sizeof an integer?
  2. Size of pid_t, uid_t, gid_t on Linux
  3. Logic behind sizeof operator [duplicate]
  4. How to find the ‘sizeof’ (a pointer pointing to an array)?
  5. What does sizeof(&array) return?
  6. Are there machines, where sizeof(char) != 1, or at least CHAR_BIT > 8?
  7. What is size_t in C?
  8. Why does a C-Array have a wrong sizeof() value when it’s passed to a function? [duplicate]
  9. newbie questions about malloc and sizeof
  10. Using sizeof with a dynamically allocated array
  11. size_t vs. uintptr_t
  12. Fast computing of log2 for 64-bit integers
  13. What does ‘sizeof (function name)’ return?
  14. Checking the size of an object in Objective-C
  15. Why is the maximum size of an array “too large”?
  16. In C, why is sizeof(char) 1, when ‘a’ is an int?
  17. Behavior of sizeof on variable length arrays (C only)
  18. How can I print the result of sizeof() at compile time in C?
  19. How can I find the number of elements in an array?
  20. x86_64 ASM – maximum bytes for an instruction?
  21. Why is (sizeof(int) > -1) false? [duplicate]
  22. C left shift on 64 bits fail
  23. Using sizeof() on malloc’d memory [duplicate]
  24. Why do I get a warning every time I use malloc?
  25. sizeof single struct member in C
  26. Implementation of sizeof operator
  27. Is the operand of `sizeof` evaluated with a VLA?
  28. why sizeof(‘a’) is 4 in C? [duplicate]
  29. C -> sizeof string is always 8
  30. Why can’t I use sizeof in a preprocessor condition?

Leave a Comment