Displaying 20 results from an estimated 1000 matches similar to: "[LLVMdev] Question on using GlobalVariable as function pointer"
2012 Dec 26
1
[LLVMdev] Using argument in another module
Hi everyone,
I am building a function that would call a function in another module,
I found this related thread
http://llvm.1065342.n5.nabble.com/Using-a-function-from-another-module-td10506.html
All my functions have prototype
int f(myStruct * c);
here comes my problems
If I have Function* f1,*f2
f2 is in another module, f1 is the function I am building.
Somewhere in f1 , I set
2012 Dec 21
2
[LLVMdev] How to print machine code of JIT IR
Hi,
I am using LLVM 3.1, and wants to print the machine code of JIT IR
I try the following method
EngineBuilder builder(&ctx.getModule());
builder.setEngineKind(EngineKind::JIT);
*
TargetMachine * tm = builder.selectTarget();
tm->Options.PrintMachineCode = true;*
engine = builder.create();
and somewhere in my code, I use
runJITonFunction();
Another question is that I am
2020 Feb 29
4
[MCJIT] messy call stack debug on x64 code in VisualStudio
Hi,
I'm using IR and MCJIT to compile a script language. I debug it with on the
fly generated .pdb files. During debugging, almost each time I step into a
function, I loose information about calling function inside the visual
studio callstack view or I have a bunch of pure addresses in the callstack
in between the current function and the calling function, for example :
2012 Oct 04
2
[LLVMdev] Problems of manipulating GEP for struct type
Hi,
I use JIT to execute the following LLVM IR,
------------------------------------------------------------------------------------------------------------
define internal fastcc i32 @L_00008120_(%struct.ThreadContext* %ThreadCtx) {
L_00000000_:
%0 = alloca i32
%1 = alloca i32
%2 = alloca %struct.ThreadContext*, align 4
store %struct.ThreadContext* %ThreadCtx, %struct.ThreadContext**
2012 Jul 26
1
[LLVMdev] Calling a function with bad signature, possible bug.
Hello,
I'm having troubles with writing a pass. In my pass I've have created a function that has two parameters - both of type i8*. Initially I wrote this function in C, that I translated it into IR, and then by using llc -march=cpp I got it's implementation in cpp code that actually inserts IR instructions. Then, I inserted this cpp code in my pass.
And in some places of a program
2013 Feb 25
2
[LLVMdev] Queries regarding function's arguments data type
Hi all,
I am working on my Master's project in security and I am trying to iterate
over the argument list of the function. Basically I need to do following
things :
1. Check data type of each argument of the argument list of the function.
2. Based on its data type like character array or integer array, pointer,
int, char, take different action.
3. I have added following code to check its
2013 Feb 25
0
[LLVMdev] Queries regarding function's arguments data type
On 2/25/13 1:44 PM, teja tamboli wrote:
> Hi all,
>
> I am working on my Master's project in security and I am trying to
> iterate over the argument list of the function. Basically I need to do
> following things :
Interesting. Just out of curiosity, can you tell us what your project
is about?
>
> 1. Check data type of each argument of the argument list of the
2020 Mar 01
2
[MCJIT] messy call stack debug on x64 code in VisualStudio
I've always just hacked support for this in to the various JITs (for
JuliaLang, in our debuginfo.cpp file), by setting the
no-frame-pointer-optim flag in the IR, then creating and populating a dummy
unwind description object in the .text section, and registering that
dynamically. Some day I hope to actually just register the .pdata/.xdata
sections with the unwinder.
PDBs are a bit different
2006 Sep 02
0
[LLVMdev] gfortran calling convention
On Fri, 1 Sep 2006, Michael McCracken wrote:
> Here's what works now, and I have a separate test case for each of these:
>
> statement functions
> intrinsic functions (print, cos, etc)
> loops, goto statments
> scalarized array operations
> function calls with *no arguments*
> simple common blocks
Great!
> Function calls with more than one argument don't work.
2006 Sep 02
2
[LLVMdev] gfortran calling convention
The NIST F77 test suite doesn't seem to be compatible with gfortran at
all, so I had to work from my own sample codes, and generate test
cases from them.
Here's what works now, and I have a separate test case for each of these:
statement functions
intrinsic functions (print, cos, etc)
loops, goto statments
scalarized array operations
function calls with *no arguments*
simple common
2010 Sep 21
1
reshape is re-ordering my variables
Is it an undocumented (at least I missed it if it's documented) feature
of the reshape function to do numeric variables followed by character?
I ask because that seems to be the case below.
> str(rcw)
'data.frame': 23 obs. of 21 variables:
$ ICU : int 1 18 17 9 22 19 6 16 25 26 ...
$ Q6.RC.1 : chr "SM" "JF" "IW"
2009 Oct 27
3
[LLVMdev] llvmgcc ToT broken
The first buildbot failure I can readily find was Monday, 26oct2009
around 7PM PDT. The assertion is
Assertion failed: ((i >= FTy->getNumParams() || FTy->getParamType(i)
== Params[i]->getType()) && "Calling a function with a bad
signature!"), function init, file /Volumes/Sandbox/Buildbot/llvm/
2008 Feb 05
1
[LLVMdev] Problem Building llvm-gcc 4.2
Dear All,
I'm getting the following error building mainline llvm-gcc 4.2 (LLVM and
llvm-gcc are up to date):
cc1: /home/vadve/criswell/src/llvm22/lib/VMCore/Instructions.cpp:290:
void llvm::CallInst::init(llvm::Value*, llvm::Value*): Assertion
`(FTy->getNumParams() == 1 || (FTy->isVarArg() && FTy->getNumParams() ==
0)) && "Calling a function with bad
2013 Jan 03
2
[LLVMdev] Opt error
Hi Team,
I am migrating one of the Pass that was written for llvm2.2 or older to llvm3.1. The code snippet looks like the following:
Constant *func;
void add( Module *M) {
func = M->getOrInsertFunction("func", Type::getVoidTy(M->getContext()), NULL);
}
virtual bool runOnModule(Module &M) {
add (&M);
for(Module::iterator F = M.begin(), E = M.end(); F !=
2009 Sep 06
3
[LLVMdev] Equivalent types
Hi!
I have this error while building my code:
Assertion failed: ((i >= FTy->getNumParams() || FTy->getParamType(i)
== Params[i]->getType()) && "Calling a function with a bad
signature!")
Actually I'm trying to load functions from .bc file and use them in
the code that I'm building with IRBuilder.
I found that function parameter type is %struct.reValue* and
2011 Sep 16
2
[LLVMdev] How to duplicate a function?
Hi all,
Sorry for the inconvenient about the previous post. The files were not
attached. So I put them here again.
I am a newbie in LLVM and I am trying to replace the function like:
old function || new function
==============================
=========
int haha(int a) { int haha(int a, char* ID) {
===>
}
2010 Jun 03
5
[LLVMdev] Why asserts don't provide much information?
When for example some call is wrong error message always looks like this:
Assertion failed: ((i >= FTy->getNumParams() || FTy->getParamType(i) ==
Params[i]->getType()) && "Calling a function with a bad signature!"),
function init, file /tmp/llvm-svn/llvm/lib/VMCore/Instructions.cpp, line
247.
I believe assert() statements should better be replaced with more
2010 Oct 06
3
[LLVMdev] dragonegg vs -ffast-math?
On Wed, Oct 06, 2010 at 02:26:35PM +0200, Duncan Sands wrote:
> Hi Jack,
>
> > I am finding that llvm 2.8 rc3 with dragonegg svn built against current
> > gcc-4_5-branch doesn't appear to allow gfortran to use -ffast-math. Attempting
> > to compile code using the dragonegg plugin under gcc 4.5.2 with that option produces the error...
> >
> > f951:
2013 Jan 03
0
[LLVMdev] Opt error
Hi Ahmad,
On 03/01/13 16:26, Hassan, Ahmad wrote:
> Hi Team,
>
> I am migrating one of the Pass that was written for llvm2.2 or older to llvm3.1.
> The code snippet looks like the following:
>
> Constant *func;
>
> void add( Module *M) {
>
> func = M->getOrInsertFunction("func", Type::getVoidTy(M->getContext()), NULL);
this function has no
2010 Apr 28
1
[LLVMdev] Constructing a varargs CallInst
I'm trying to use CallInst::Create to construct a call to a variadic
function, and I'm running into the following assertion failure:
/localhome/simmon12/workspace/llvm-sources/lib/VMCore/Instructions.cpp:297:
void llvm::CallInst::init(llvm::Value*, llvm::Value* const*, unsigned
int): Assertion `(i >= FTy->getNumParams() || FTy->getParamType(i) ==
Params[i]->getType())