Undefined behavior: What happened to my code?

Proceedings of the Asia-Pacific Workshop on Systems, APSYS'12

Volumn , Issue , 2012, Pages

  Wang, Xi ^a   Chen, Haogang ^a   Cheung, Alvin ^a   Jia, Zhihao ^b   Zeldovich, Nickolai ^a   Kaashoek, M Frans ^a  

^a MASSACHUSETTS INSTITUTE OF TECHNOLOGY   (United States)

^b TSINGHUA UNIVERSITY   (China)

Author keywords

[No Author keywords available]

Indexed keywords

COMPILER WRITERS; LANGUAGE CONSTRUCTS; POSITION PAPERS; REAL-WORLD SYSTEM; RESEARCH COMMUNITIES; SECURITY VULNERABILITIES; SPECIFIC INSTRUCTION;

COMPUTER SYSTEMS PROGRAMMING;

C (PROGRAMMING LANGUAGE);

EID: 84866981334     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1145/2349896.2349905     Document Type: Conference Paper

References (28)

1. Common vulnerabilities and exposures (CVE). http://cve.mitre.org/.
2. assert(int+100 > int) optimized away. Bug 30475, GCC, 2007. http://gcc.gnu.org/bugzilla/show-bug.cgi?id=30475.
3. C compilers may silently discard some wraparound checks. Vulnerability Note VU#162289, US-CERT, 2008. http://www.kb.cert.org/vuls/id/162289.
4. ext4: fixpoint divide exception at ext4-fill-super. Bug 14287, Linux kernel. 2009. https://bugzilla.kernel.org/show-bug.cgi?id=14287.
5. postgresq1-9.0: FTBFS on sparc64, testsuite issues with int8. Bug 616180, Dehian, 2011. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616180.
6. D. Berlin. Re: changing "configure" to default to "gcc -g -O2 -fwrapv ...". http://lists.gnu.org/archive/html/autoconf-patches/2006- 12/msg00149.html, 2006.
7. J. Bloch and N. Gafter. Java Puzzlers: Traps, Pitfalls, and Corner Cases. Addison-Wesley Professional, 2005.
8. C. Cadar, D. Dunbar, and D. Engler. KLEE: Unassisted and automatic generation of high-coverage tests for complex systems programs. In Proc. of the 8th OSDI, San Diego, CA, December 2008.
9. J. Corbet. Fun with NULL pointers, part 1. http://lwn.net/Articles/ 342330/, 2009.
10. R. Cox. Re: plan9port build failure on Linux (debian). http://9fans.net/archive/2008/03/89, 2008.
11. W. Diets, P. Li, J. Regehr, and V. Adve. Understanding integer overflow in C/C++. In Proc. of the 34th ICSE, pages 760-770, Zurich, Switzerland, June 2012.
12. C. Ellison and G. Roşu. An executable formal semantics of C with applications. In Proc. of the 39th POPL, pages 533-544, Philadelphia, PA, January 2012.
13. C. Ellison and G. Roşu. Defining the undefinedness of C. Technical report, University of Illinois, April 2012.
14. D. Gohman. The nsw story. http://lists.cs.uiuc.edu/pipermail/llvmdev/ 2011-November/045730.html, 2011.
15. Power ISA. IBM, 2010. http://www.power.org/.
16. Intel Itanium Architecture Software Developer's Manual, Volume 1: Application Architecture. Intel, 2010.
17. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2: Instruction Set Reference. Intel, 2012.
18. ISO/IEC TR 18037:2006. Programming languages - C - Extensions to support embedded processors. ISO/IEC, 2006.
19. ISO/IEC 9899:2011, Programming languages - C. ISO/IEC, 2011.
20. B. Jack. Vector rewrite attack: Exploitable NULL pointer vulnerabilities on ARM and XScale architectures. In CanSecWest 2007, Vancouver, BC, Canada, April 2007.
21. C. Lattner. What every C programmer should know about undefined behavior #3/3. http://blog.llvm.org/2011/05/what-every-c-programmer-should-know-21.html, 2011.
22. C. Price. MIPS IV Instruction Set. MIPS Technologies, 1995.
23. J. Regehr. A guide to undefined behavior in C and C++, part 3. http://blog.regehr.org/archives/232, 2010.
24. B. Rosenkränzer. Compiler flags used to speed up Linaro Android 2011.10, and future optimizations. http://www.linaro.org/linaro-blog/2011/10/25/ compiler-flags-used-to-speed-up-linaro-android-2011-10-and-future-optimizations/ , 2011.
25. M. Sipser. Introduction to the Theory of Computation. Cengage Learning, second edition, 2005.
26. I. L. Taylor. Signed overflow. http://www.airs.com/blog/archives/120, 2008.
27. J. Tourrilhes. Invalid compilation without -fno-strict-aliasing. http://lkml.org/lkml/2003/2/25/270, February 2003.
28. J. F. Woods, Re: Why is this legal? http://groups.google.com/group/comp. std.c/msg/dfe1ef367547684b, 1992.