News for hackers. Stuff that matters.
Re:What Every C Programmer Should Know About Undefined Behav... by peterbotond on Saturday May 14, 2011 @07:51PM (#2548881)
the way to write good solid code is to use more than 2 compiler, and optimisation etc. i mostly write code that runs on at least 3 different os, and 2 different hardware. ... and it just works. no prog-lang can be faulted for bad programming using one. learn the lang, and use it. :-)

gcc still gets the pointer dereference and assignment to what a pointer points to, due to deferring assignments. these edges, idioms of any lang needs to be looked at with academic eyes. :-)

Re:What Every C Programmer Should Know About Undefined Behav... by astrange on Saturday May 14, 2011 @10:34PM (#2549152)
Do you fuzz your inputs? Run with the clang undefined integer overflow checker? Run your program on hardware with 16-bit int?
Re:What Every C Programmer Should Know About Undefined Behav... by peterbotond on Sunday May 15, 2011 @09:47AM (#2549935)
yes, random bits flipped on good input. yes, i run anything that can help me and covers the problem. nowadays, 32 and 64 bit are what i write code for. oh, the days of 16bit ints on win3.11 for workgroups are gone. :-)

llvm is an excellent tool, hats off, and thanks.