diff options
author | Garrison Venn <gvenn.cfe.dev@gmail.com> | 2011-04-12 12:30:10 +0000 |
---|---|---|
committer | Garrison Venn <gvenn.cfe.dev@gmail.com> | 2011-04-12 12:30:10 +0000 |
commit | 18bba84d7782e978caebddbd98b39e555c63b4dc (patch) | |
tree | 91dcd8a42a27ff0fa80587070535bcfac61a9e77 /examples | |
parent | d0aacbcc2e60fd06652280a9105eb2f8f9378efc (diff) |
Added new FIXME note
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@129360 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'examples')
-rw-r--r-- | examples/ExceptionDemo/ExceptionDemo.cpp | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/examples/ExceptionDemo/ExceptionDemo.cpp b/examples/ExceptionDemo/ExceptionDemo.cpp index fcc8b5c790..5fa10ed6d3 100644 --- a/examples/ExceptionDemo/ExceptionDemo.cpp +++ b/examples/ExceptionDemo/ExceptionDemo.cpp @@ -62,7 +62,16 @@ #include "llvm/Support/IRBuilder.h" #include "llvm/Support/Dwarf.h" +// FIXME: Although all systems tested with (Linux, OS X), do not need this +// header file included. A user on ubuntu reported, undefined symbols +// for stderr, and fprintf, and the addition of this include fixed the +// issue for them. Given that LLVM's best practices include the goal +// of reducing the number of redundant header files included, the +// correct solution would be to find out why these symbols are not +// defined for the system in question, and fix the issue by finding out +// which LLVM header file, if any, would include these symbols. #include <cstdio> + #include <sstream> #include <stdexcept> |