defining __STDC_LIMIT_MACROS on the command line is not really necessary for Visual Studio, and is a bit of a pain when you want to include the LLVM headers from your own project, so I moved the check a bit down into the Unix case to avoid the hassle... Here is a patch On a side note, everything is going well so far with integrating LLVM into our application - I was very happy when I found out I could use 'addGlobalMapping' to pass larger structures into the ExecutionEngine without copying, and also to add functions from our own application. If there are any problems with this approach, please tell me... m. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: diff.txt URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20041103/8cb89ecb/attachment.txt>
On Wed, 3 Nov 2004, Morten Ofstad wrote:> defining __STDC_LIMIT_MACROS on the command line is not really necessary > for Visual Studio, and is a bit of a pain when you want to include the > LLVM headers from your own project, so I moved the check a bit down into > the Unix case to avoid the hassle... Here is a patchOk, makes sense!> On a side note, everything is going well so far with integrating LLVM > into our application -Great!> I was very happy when I found out I could use > 'addGlobalMapping' to pass larger structures into the ExecutionEngine > without copying, and also to add functions from our own application. If > there are any problems with this approach, please tell me...Yup, that should be no problem, just make sure that the LLVM view of the data matches the data layout (i.e., the LLVM type matches). -Chris -- http://llvm.org/ http://nondot.org/sabre/
Maybe Matching Threads
- [LLVMdev] Small patch for visual studio project files
- [LLVMdev] FP Constants spilling to memory in x86 code generation
- [LLVMdev] Small patch for visual studio project files
- [LLVMdev] Small patch for visual studio project files
- [LLVMdev] Final Visual Studio Patches