GCC Flags

-Wall -Wextra -ansi -pedantic bitch!

>>49
Enjoy your broken executables.

>>51
I alreaSegmentation fault

-O4 -s

>>38
Are you saying that you're doing a better job emulating the C abstract machine than my implementation is?

gcc -get -dubs

-g -Wall -Werror -Wextra -pedantic -pedantic-errors -std=c99

MASTER RACE

>>56
c99
Nope.

>>57
not using c99
Enjoy not legally having stdint.h. That's the only reason why I use c99. The rest of the features are bullshit.

>>58
Please do tell me why anyone would need stdint.h, it isn't even implemented on Windows since it's so useless.

>>59
Ask frozen void.

>>60
Funny joke, FrozenVoid doesn't even use stdint.h, he just assumes that everybody is running the same compiler/architecture/OS as he is and makes his own flawed defines.

>>59
You're a mental midget. You want to know why? It's because the standard integral types are defined as 'one byte', 'at least two bytes', 'at least two bytes', 'at least four bytes' and 'at least eight bytes' for char, short, int, long and long long respectively. What if I want the largest possible ((u)intmax_t)? What if I want an exact type ((u)intn_t), say, if I want to work with binary file formats or network protocols without size definitions breaking between architectures? Picture this: I'm reading a file into a struct, and one of the struct's fields needs to be four bytes. What type do I use? Hint: it's not int, because that can be 2 bytes, and it's not long, as on LP64 platforms, it's 8 byted.

>>62
YHBT

>>63
;_;

>>62
I can't believe the day has come,  but I actually agree with Kodak. Not that you couldn't unofficially hack it together in C90 using structs, sizeofs and void pointers, but why bother if the work has already been done and standardized?

DUBS, DUBS EVERYWHERE!