更新:c++ 11将TR1中的类型正式引入标准:

Long Long int Unsigned long long int

以及<cstdint>中的"size "类型

int8_t int16_t int32_t int64_t (以及未签名的副本)。

另外，你会得到:

int_least8_t int_least16_t int_least32_t int_least64_t 加上未签名的对应项。

这些类型表示至少具有指定位数的最小整数类型。同样，也有“最快”的整数类型，至少具有指定的比特数:

int_fast8_t int_fast16_t int_fast32_t int_fast64_t 加上无符号的版本。

“快”意味着什么，如果有的话，取决于实现。它也不需要在所有方面都是最快的。

实际上没有这样的事情。通常，std::size_t表示当前体系结构上的无符号本机整数大小。即16位、32位或64位，但并不总是如此，就像这个答案的评论中指出的那样。

至于所有其他内置类型，它实际上取决于编译器。以下是摘自最新c++标准的当前工作草案的两段摘录:

There are five standard signed integer types : signed char, short int, int, long int, and long long int. In this list, each type provides at least as much storage as those preceding it in the list. For each of the standard signed integer types, there exists a corresponding (but different) standard unsigned integer type: unsigned char, unsigned short int, unsigned int, unsigned long int, and unsigned long long int, each of which occupies the same amount of storage and has the same alignment requirements.

如果您愿意，您可以静态(编译时)断言这些基本类型的sizeof。如果假设的大小发生变化，它会提醒人们考虑移植您的代码。

如前所述，大小应该反映当前的体系结构。如果你想知道当前编译器是如何处理的，你可以在limits.h中取一个峰值。

正如其他人回答的那样，“标准”都将大部分细节保留为“实现定义的”，只声明类型“char”的宽度至少为“char_bis”，并且“char <= short <= int <= long <= long long”(浮点数和双精度浮点数与IEEE浮点标准基本一致，长双精度浮点数通常与双精度浮点数相同——但在更当前的实现中可能更大)。

Part of the reasons for not having very specific and exact values is because languages like C/C++ were designed to be portable to a large number of hardware platforms--Including computer systems in which the "char" word-size may be 4-bits or 7-bits, or even some value other than the "8-/16-/32-/64-bit" computers the average home computer user is exposed to. (Word-size here meaning how many bits wide the system normally operates on--Again, it's not always 8-bits as home computer users may expect.)

If you really need a object (in the sense of a series of bits representing an integral value) of a specific number of bits, most compilers have some method of specifying that; But it's generally not portable, even between compilers made by the ame company but for different platforms. Some standards and practices (especially limits.h and the like) are common enough that most compilers will have support for determining at the best-fit type for a specific range of values, but not the number of bits used. (That is, if you know you need to hold values between 0 and 127, you can determine that your compiler supports an "int8" type of 8-bits which will be large enought to hold the full range desired, but not something like an "int7" type which would be an exact match for 7-bits.)

注意:使用了许多Un*x源包”。/configure”脚本，它将探测编译器/系统的功能，并输出一个合适的Makefile和config.h。您可以检查其中一些脚本，看看它们是如何工作的，以及它们如何探测编译器/系统功能，并遵循它们的指导。

当涉及到不同架构和不同编译器的内置类型时，只需在你的架构上用编译器运行以下代码，看看它输出了什么。下面是我的Ubuntu 13.04 (Raring Ringtail) 64位g++4.7.3输出。还请注意下面的回答，这就是为什么输出是这样排序的:

有五种标准的有符号整型:有符号char、short int、int、long int和long long int。在此列表中，每种类型提供的存储空间至少与列表中前面的类型相同。”

#include <iostream>

int main ( int argc, char * argv[] )
{
  std::cout<< "size of char: " << sizeof (char) << std::endl;
  std::cout<< "size of short: " << sizeof (short) << std::endl;
  std::cout<< "size of int: " << sizeof (int) << std::endl;
  std::cout<< "size of long: " << sizeof (long) << std::endl;
  std::cout<< "size of long long: " << sizeof (long long) << std::endl;

  std::cout<< "size of float: " << sizeof (float) << std::endl;
  std::cout<< "size of double: " << sizeof (double) << std::endl;

  std::cout<< "size of pointer: " << sizeof (int *) << std::endl;
}


size of char: 1
size of short: 2
size of int: 4
size of long: 8
size of long long: 8
size of float: 4
size of double: 8
size of pointer: 8

对于32位系统，“事实上”的标准是ILP32——也就是说，int、long和pointer都是32位的量。

对于64位系统，主要的Unix“事实上”标准是LP64 -长和指针是64位(但int是32位)。Windows 64位标准是LLP64 - long long和pointer是64位(但long和int都是32位)。

曾经，一些Unix系统使用ILP64组织。

这些事实上的标准没有一个是由C标准(ISO/IEC 9899:1999)立法的，但都是被C标准所允许的。

并且，根据定义，sizeof(char)是1，尽管在Perl配置脚本中进行了测试。

注意，有些机器(Crays) CHAR_BIT远大于8。这意味着，IIRC sizeof(int)也是1，因为char和int都是32位的。