similar to: [LLVMdev] [PATCH] bugpoint: pass -load options to LLI

Hi Eli, Thanks for the reply. I tried with -Xlinker="-ldl ". However it does not seem to make a difference. It seems that when bugpoint is run with --run-jit, the linker args are not passed to gcc (from tools/bugpoint/ExecutionDriver.cpp) : if (InterpreterSel == RunLLC || InterpreterSel == RunCBE || InterpreterSel == CBE_bug || InterpreterSel == LLC_Safe) RetVal =

Hi Prakash, Unfortunately it looks like you need to do quite a bit of investigation into this. However, I hope I can provide some useful tips. 1. In general, lli and llc generate exact the same code except lli default to static codegen while llc defaults to dynamic-no-pic codegen. So try passing -relocation-model=dynamic-no-pic to lli. If this works, that means there are issues with

I've filed PR3043 for this. Evan On Nov 3, 2008, at 4:00 PM, Prakash Prabhu wrote: > Hi Evan, > > Thanks for the pointers. We found a simple test case that causes the > problem (thanks to Tom in my group): > > #include<stdio.h> > #include<stdlib.h> > > void test(); > void (*funcPtr)(); > > int main(int argc, char **argv) { > funcPtr =

Hi, when reporting http://llvm.org/bugs/show_bug.cgi?id=5104 I spent quite a while trying to figure out what passes are used by "-O1" so that I could give this list to bugpoint. It turns out -debug-pass=Arguments is mentioned in docs/HowToSubmitABug.html but under a chapter titled "Compile-time optimization bugs" which I naively ignored since my bug was not a compile-time

On Tue, Oct 28, 2008 at 12:17 PM, Prakash Prabhu <prakash.prabhu at gmail.com> wrote: > Generating reference output from raw program: <cbe><gcc> > Error running tool: [snip] > /tmp/cc08IpX8.o: In function `SyLoadModule': > bugpoint-test-program.bc.cbe.c:(.text+0x25705): undefined reference to > `dlopen' [snip] This is saying that compilation with CBE is

Hi Evan, Thanks for the pointers. We found a simple test case that causes the problem (thanks to Tom in my group): #include<stdio.h> #include<stdlib.h> void test(); void (*funcPtr)(); int main(int argc, char **argv) { funcPtr = test; test(); } void test() { if(funcPtr == test) { printf("OK!\n"); } else { fprintf(stderr, "Bad!\n"); exit(1);

Hi, I have a program that runs when statically compiled using llc and gcc but crashes with a segmentation fault when run with lli. I am trying to debug it with bugpoint and the initial part of bugpoint seems to be suggesting that I am somehow missing the linking with the libraries having dlsym/dlopen although I am passing it to lli : *$ bugpoint -run-jit

Hello, David > bugpoint now works for remote ARM if you run it directly from the > command line. It doesn't work correctly when invoked from the test > makefile because envvar PWD is being set to /bin/pwd and so causing > GCC::ExecuteProgram to do the wrong thing. I'm not sure what is going > on with that, perhaps something in the makefile hierarchy is setting > PWD to

I just checked in my changes to bugpoint and Makefile.programs in the test suite. These changes shouldn't conflict with yours. revision 75292 revision 75293 bugpoint now works for remote ARM if you run it directly from the command line. It doesn't work correctly when invoked from the test makefile because envvar PWD is being set to /bin/pwd and so causing GCC::ExecuteProgram to

> I will investigate. I'm in the middle of it as well. Best regards, Viktor ----- Original Message ----- From: "David Goodwin" <david_goodwin at apple.com> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Friday, July 10, 2009 2:43 PM Subject: Re: [LLVMdev] Heads up! Working on bugpoint >I just checked in my changes to bugpoint and

Timo Juhani Lindfors wrote: > Nick Lewycky<nicholas at mxc.ca> writes: >> The interpreter uses libffi to make external function calls. However, it >> needs to be detected at LLVM's compile time. If you're using the >> released packages, we disabled that because we were worried about users >> who don't have libffi installed. > > This seems to be

I am currently running on a Mac OSX 10.3.8 and trying to compile llvm-1.4 on my local machine for Prof. Adve's class. I am using Apple's provided gcc 3.3 as my compiler. I ran into this compile error: SysUtils.c: In function `executeProgram': SysUtils.c:119: error: `RTLD_NEXT' undeclared (first use in this function) SysUtils.c:119: error: (Each undeclared identifier is reported

Hi Nick: Thanks for pointing me to libffi. Recompile LLVM with libffi does solve the problem of printf. But it still has other problems: 1) sinf() returns 0 in the interpreter, but returns correct value in JIT (see hellosin.c) 2) calling pthread_create cause lli to crash in the interpreter mode, but no problem in JIT (see phello.c). My questions are: i) can I call any arbitrary external function

Hi Nick: The first problem have been solved by calling llvm-ld: $ llvm-ld -o hellosin.llvm hellosin.bc -lm $ lli -force-interpreter=true -load=/usr/lib/libm.so hellosin.llvm.bc hello sin: 0.50 The pthread problem remains after llvm-ld: $ lli -force-interpreter=true -load=/lib/libpthread.so.0 phello.llvm.bc 0 lli 0x08796bf8 Segmentation fault For those who are getting "invalid

It seems that bugpoint (and llvmc2, etc.) is hard-wired to use gcc to do assembling and linking. I want to bugpoint-reduce a testcase that came from Fortran and so I need to invoke our compiler to do at least the linking step to get our Fortran libraries. Is there a way to do this via bugpoint's command-line interface or do I have to hack bugpoint's source? I can see how I might make

On Tue, 27 Sep 2005, Kevin J. Stephano wrote: > I am currently running on a Mac OSX 10.3.8 and trying to > compile llvm-1.4 on my local machine for Prof. Adve's class. > > I am using Apple's provided gcc 3.3 as my compiler. > > I ran into this compile error: > SysUtils.c: In function `executeProgram': > SysUtils.c:119: error: `RTLD_NEXT' undeclared (first

On Mon, Mar 20, 2017 at 9:58 PM, Timo Juhani Lindfors <timo.lindfors@iki.fi> wrote: > ıuoʎ <yonjah@gmail.com> writes: >> I have a host running a few guests all configured to autostart. >> I'm also using libvirt-guests to suspend the guests when the host >> restarts or shuts down > > I have a similar setup. I solved it by writing a small daemon that syncs

Hi Nick: Thanks for the response. You are right about sinf. I changed the constant to sscanf(argv[1], ...), and it gave me back 0 again. I also compared the disassembled code, and saw it was indeed the case. The primary reason I use interpreter is because I wish to do runtime checking on memory access pattern in multithreaded C programs. for example, if thread one is in the critical section, I

* Timo Juhani Lindfors (timo.lindfors at iki.fi) wrote: > Hi, > > Alexandre Gouraud <alexandre.gouraud at enst-bretagne.fr> writes: > > if it does not already exists, could it mean it is a nonsense, then why? > > Why don't you compile your program directly to LLVM bitcode? - In security-testing you sometimes apply black boxing. I've had a similar idea

On Thu, Oct 15, 2009 at 7:14 AM, Timo Juhani Lindfors <timo.lindfors at iki.fi> wrote: > Tianwei <tianwei.sheng at gmail.com> writes: >> someone suggested me to use gold-plugin, I know nothing about it yet, I will >> have a try later.  Does anyone have a good solution for this problem? > > Afaik gold does not help here. I tried it and managed to only generate >