Displaying 4 results from an estimated 4 matches for "foofunc".
2007 Jan 31
2
Problems with definitions of S4-generics
...006-12-19) w/ R.app 1.18
Last December, Simon Urbanek confirmed that the issue is not platform
related, and that it is most likely a bug. He suggested to post my report
to "the appropriate mailing list" -- I choose r-devel.
#### Problem-intro:
## Define two S4-classes
setGeneric("foofunc", def=function(object) {standardGeneric("foofunc")})
setGeneric("barfunc", def=function(object) {standardGeneric("barfunc")})
#### Okay, let's start.
#### Fist the correct part
## Do some tests to see if the generic is present,
## and have a look at some det...
2011 Nov 25
2
[LLVMdev] LLVM 2.9 - JIT problem on Windows
...,
> but to no avail. Nothing wrong with 'my' LLVM code... Frustrating!
FWIW, I have simplified 'my' LLVM code to just:
llvm::InitializeNativeTarget();
llvm::LLVMContext context;
llvm::Module *module = new llvm::Module("test", context);
llvm::Function *fooFunc =
llvm::cast<llvm::Function>(module->getOrInsertFunction("foo",
llvm::Type::getVoidTy(context),
(llvm::Type *) 0));
llvm::BasicBlock *basicBlock = llvm::BasicBlock::Create(context,
"entryBlock", fooFunc);
llvm::ReturnInst::Create(context, basicBlock);...
2011 Nov 25
0
[LLVMdev] LLVM 2.9 - JIT problem on Windows
> > > Now, I may be wrong, but I was under the impression that a call to
> > > InitializeNativeTarget was recommended, if not compulsory, so. why
> > > commenting it out not only makes my LLVM code still work, but also
> > > prevent my application from generating the above error.?!
> >
> > My bet is that your code is writing through a stray pointer.
2011 Nov 25
2
[LLVMdev] LLVM 2.9 - JIT problem on Windows
> > Now, I may be wrong, but I was under the impression that a call to
> > InitializeNativeTarget was recommended, if not compulsory, so. why
> > commenting it out not only makes my LLVM code still work, but also
> > prevent my application from generating the above error.?!
>
> My bet is that your code is writing through a stray pointer. By removing the
> call to