Check out my first novel, midnight's simulacra!
ISO C: Difference between revisions
From dankwiki
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
==[[GCC|gcc]] | ==Compilers== | ||
* I'd like to [http://gcc.gnu.org/c99status.html | * Intel's [http://software.intel.com/en-us/intel-compilers/ C/C++ Compiler] (icc) is [http://software.intel.com/en-us/articles/non-commercial-software-download/ free for non-commercial development] | ||
* AMD's [http://developer.amd.com/cpu/open64/pages/default.aspx Open64 Compiler Suite] is just plain free | |||
===[[GCC|gcc]]=== | |||
* I'd like to further along [http://gcc.gnu.org/c99status.html gcc C99 support] | |||
==Threads== | ==Threads== | ||
Revision as of 06:33, 4 October 2009
Compilers
- Intel's C/C++ Compiler (icc) is free for non-commercial development
- AMD's Open64 Compiler Suite is just plain free
gcc
- I'd like to further along gcc C99 support
Threads
- Hans Boehm's Threads and Memory Model for C++ page is awesome
Aliasing
- See Compiler Design page
- -O2 implies -fstrict-aliasing, at least as of gcc 4.3
- -Wstrict-aliasing=2 warns about many constructions unsafe to use with -fstrict-aliasing
- How to use Berkeley sockets API? See http://archives.free.net.ph/message/20080529.200047.b40321b6.fi.html, etc
stdint.h
An awesome addition. Type constructions of the form u?int{variety}_t (u prefix denotes unsigned). Varieties include:
- ptr: Size sufficient to hold a pointer. This is useful for function type definitions, when it's unsure whether a pointer or integer type would be most appropriate for various instances (a void *'s size is not directly related to an int's size by the ANSI C standard).
- max: Size sufficient to hold any other integer type.
- fast{8,16,32,64}: Fastest integer type having at least the specified width.
- least{8,16,32,64}: Minimum native integer type having at least the specified width.
- {8,16,32,64}: Integer type having precisely this width.
