Displaying 5 results from an estimated 5 matches for "raw_stdout_ostream".
2009 Oct 06
0
[LLVMdev] 2.6/trunk Execution Engine question
...nclude "llvm/Support/raw_os_ostream.h"
#include "llvm/Bitcode/ReaderWriter.h"
#include "llvm/Support/raw_ostream.h"
#include "llvm/Target/TargetSelect.h"
#include "llvm/ExecutionEngine/JIT.h"
#include <assert.h>
using namespace llvm;
static raw_stdout_ostream raw_cout;
int main(int argc, char** argv)
{
// Test JITting a variable without JITting any functions.'
Module* mod = new Module("test", getGlobalContext());
GlobalVariable* gv = cast<GlobalVariable>(mod->getOrInsertGlobal("TestGV",
Type::getInt32Ty(getGlobalC...
2009 Oct 06
1
[LLVMdev] 2.6/trunk Execution Engine question
On Tue, Oct 6, 2009 at 5:49 PM, Reid Kleckner <rnk at mit.edu> wrote:
>> Also, the null pointer is coming from a call to JCE->allocateSpace().
>> This is a virtual function; I'm trying to discover what subclass it
>> is.
>
> So, there's JITEmitter::allocateSpace which overrides
> JITCodeEmitter::allocateSpace(), but *most* of the time it just calls
>
2009 Aug 23
0
[LLVMdev] LLVMContext: Suggestions for API Changes
On Aug 23, 2009, at 4:29 PM, Albert Graef <Dr.Graef at t-online.de> wrote:
>
> One thing I noticed is that writing LLVM assembler code (print()
> methods) seems to be horribly slow now (some 4-5 times slower than in
> LLVM 2.5). This is a real bummer for me, since Pure's batch compiler
> uses those methods to produce output code which then gets fed into
> llvmc.
>
2009 Oct 06
4
[LLVMdev] 2.6/trunk Execution Engine question
> 6. When ExecutionEngine::create was called with parameter
> "GVsWithCode" set to its default value of true, I got a segfault when
> trying to get a pointer to one of my globals. JIT::getMemoryForGV was
> returning NULL in that case. Explicitly passing false for
> "GVsWithCode" cleared it up.
That's no good. Could you send me a stack trace and explain
2009 Aug 23
4
[LLVMdev] LLVMContext: Suggestions for API Changes
Jeffrey Yasskin wrote:
> See Owen's email about docs for the 2.6 release, but it's really not
> that hard to keep up with trunk. I recently merged trunk LLVM into
> Unladen Swallow, and the changes I needed to make are at
> http://code.google.com/p/unladen-swallow/source/detail?r=724.
Thanks Jeffrey, that was really very helpful! I have Pure working with
both the LLVM 2.6