+- 0Day Forums (https://0day.red)
+-- Forum: Coding (https://0day.red/Forum-Coding)
+--- Forum: C# (https://0day.red/Forum-C)
+--- Thread: Specifying size of enum type in C (/Thread-Specifying-size-of-enum-type-in-C)
Specifying size of enum type in C - Mrbluffer349 - 07-24-2023
Already read through [this related question][1], but was looking for something a little more specific.
- Is there a way to tell your compiler specifically how wide you want your enum to be?
- If so, how do you do it? I know how to specify it in C#; is it similarly done in C?
- Would it even be worth doing? When the enum value is passed to a function, will it be passed as an `int`-sized value regardless?
[1]:
[To see links please register here]
RE: Specifying size of enum type in C - undersplice636342 - 07-24-2023
I believe there is a flag if you are using GCC.
> -fshort-enums
RE: Specifying size of enum type in C - paramountcies772010 - 07-24-2023
You can force it to be at least a certain size by defining an appropriate value. For example, if you want your enum to be stored as the same size as an `int`, even though all the values would fit in a `char`, you can do something like this:
typedef enum {
firstValue = 1,
secondValue = 2,
Internal_ForceMyEnumIntSize = MAX_INT
} MyEnum;
Note, however, that the behavior can be dependent on the implementation.
As you note, passing such a value to a function will cause it to be expanded to an int anyway, but if you are using your type in an array or a struct, then the size will matter. If you really care about element sizes, you should really use types like `int8_t`, `int32_t`, etc.
RE: Specifying size of enum type in C - moderate499021 - 07-24-2023
> Is there a way to tell your compiler
> specifically how wide you want your
> enum to be?
In general case no. Not in standard C.
> Would it even be worth doing?
It depends on the context. If you are talking about passing parameters to functions, then no, it is not worth doing (see below). If it is about saving memory when building aggregates from enum types, then it might be worth doing. However, in C you can simply use a suitably-sized integer type instead of enum type in aggregates. In C (as opposed to C++) enum types and integer types are almost always interchangeable.
> When the enum value is passed to a function, will it be passed as an int-sized value regardless?
Many (most) compilers these days pass all parameters as values of natural word size for the given hardware platform. For example, on a 64-bit platform many compilers will pass all parameters as 64-bit values, regardless of their actual size, even if type `int` has 32 bits in it on that platform (so, it is not generally passed as "int-sized" value on such a platform). For this reason, it makes no sense to try to optimize enum sizes for parameter passing purposes.
RE: Specifying size of enum type in C - nonpartisan48123 - 07-24-2023
It depends on the values assigned for the enums.
Ex:
If the value greater than 2^32-1 is stored, the size allocated for the overall enum will change to the next size.
Store 0xFFFFFFFFFFFF value to a enum variable, it will give warning if tried to compile in a 32 bit environment (round off warning)
Where as in a 64 bit compilation, it will be successful and the size allocated will be 8 bytes.
RE: Specifying size of enum type in C - fayelaesqobhg - 07-24-2023
Even if you are writing strict `C` code, the results are going to be compiler dependent. Employing the strategies from this thread, I got some interesting results...
**enum_size.c**
```c
#include <stdio.h>
enum __attribute__((__packed__)) PackedFlags {
PACKED = 0b00000001,
};
enum UnpackedFlags {
UNPACKED = 0b00000001,
};
int main (int argc, char * argv[]) {
printf("packed:\t\t%lu\n", sizeof(PACKED));
printf("unpacked:\t%lu\n", sizeof(UNPACKED));
return 0;
}
```
```nano
$ gcc enum_size.c
$ ./a.out
packed: 4
unpacked: 4
```
```nano
$ gcc enum_size.c -fshort_enums
$ ./a.out
packed: 4
unpacked: 4
```
```nano
$ g++ enum_size.c
$ ./a.out
packed: 1
unpacked: 4
```
```nano
$ g++ enum_size.c -fshort_enums
$ ./a.out
packed: 1
unpacked: 1
```
In my example above, I did not realize any benefit from `__attribute__((__packed__))` modifier until I started using the C++ compiler.
**EDIT:**
@technosaurus's suspicion was correct.
By checking the size of `sizeof(enum PackedFlags)` instead of `sizeof(PACKED)` I see the results I had expected...
```c++
printf("packed:\t\t%lu\n", sizeof(enum PackedFlags));
printf("unpacked:\t%lu\n", sizeof(enum UnpackedFlags));
```
I now see the expected results from `gcc`:
```nano
$ gcc enum_size.c
$ ./a.out
packed: 1
unpacked: 4
```
```nano
$ gcc enum_size.c -fshort_enums
$ ./a.out
packed: 1
unpacked: 1
```