similar to: [LLVMdev] error open a share library generated by a LLVM pass

I'm running into a completely different problem. When I do: opt -load LowerFastInvoke.o -help I get the message: Error opening 'LowerFastInvoke.o': LowerFastInvoke.o: only ET_DYN and ET_EXEC can be loaded? Am I missing something?

Hello Rui, I'm enabling the LLD in the Uefi firmware edk2 build. I meet a problem about the -pie option and cannot output the executable type obj file correctly. I need your advice. The Uefi firmware executable binary is the position independent + small code mode in 64bits. So we always add the options "-Wl,-pie -mcmodel=small" in our clang build toolchain. These options work well

On Mon, Jul 20, 2009 at 6:37 AM, Kenneth Uildriks<kennethuil at gmail.com> wrote: > I'm running into a completely different problem.  When I do: > > opt -load LowerFastInvoke.o -help > > I get the message: > > Error opening 'LowerFastInvoke.o': LowerFastInvoke.o: only ET_DYN and > ET_EXEC can be loaded? > > Am I missing something? Assuming the

Oops. Thanks... I totally missed that. On Mon, Jul 20, 2009 at 9:00 AM, Eli Friedman<eli.friedman at gmail.com> wrote: > On Mon, Jul 20, 2009 at 6:37 AM, Kenneth Uildriks<kennethuil at gmail.com> wrote: >> I'm running into a completely different problem.  When I do: >> >> opt -load LowerFastInvoke.o -help >> >> I get the message: >> >>

Here's a small test program to find out where a klibc executable expects its shared library (or interpreter to be precise) to be. It should work regardless of 32/64 bit, little- or big-endian, but only on native executables. If you have access to a 64-bit or big endian machine, I would appreciate feedback on whether it produces correct answers on your machine. To run the test, cut the

Thanks Bill! But it does not work. I get the error given below when I try to load LLVMExecutionEngine.o in the opt command. Error opening '../../../build/Release/lib/LLVMExecutionEngine.o': ../../../build/Release/lib/LLVMExecutionEngine.o: only ET_DYN and ET_EXEC can be loaded -load request ignored. Any ideas?? Please help me out here. Thanks, Bhavani --- On Sun, 10/26/08, Bill

Hello, I want to know if LLVM support static taint analysis now ? and how to implement static taint analysis code in term of LLVM pass or something else ? can anyone help me?Thank you very much! zhaoqian -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150717/0236bed3/attachment.html>

Hi John, That worked for me. I am using llvm 3.2 only and following http://safecode.cs.illinois.edu/docs/Install.html So for I am able to make inside llvm/projects/poolalloc by doing such cosmetic changes. Now, when I tried to make inside llvm/projects/safecode, I see another error. kpawar at KPAWAR-LT ~/SAFECode/LLVM_SRC/llvm/projects/safecode $ /usr/bin/clang -cc1 -triple

Kostya, I think I've found what looks like a reproducible bug in libFuzzer. The code under test is built with ASan and the first ASan CHECK failure shows fuzzer in the stack trace. (see below) One of the factors that may be unique in my testing is that each iteration can take a very long time to execute (tens or hundreds of seconds). Let me know if you need more info, I think it

Kostya, Here's the git repo: https://bitbucket.org/ebadf/fuzzpy I've only tested it on arm7 and x86_64 linux, I expect there's a good chance it may not work on other OSs. If you can build it successfully ("./build.sh", requires clang and clang++ in your path), then you should run the "testemail" case like so: while true; do ITERS=1000 ./run.sh

Ah, yes -- you need to clone with --recursive. I will try the workaround though. On Dec 3, 2015 1:12 PM, "Kostya Serebryany" <kcc at google.com> wrote: > > > On Wed, Dec 2, 2015 at 7:17 PM, Brian Cain <brian.cain at gmail.com> wrote: > >> Kostya, >> >> Here's the git repo: https://bitbucket.org/ebadf/fuzzpy >> >> I've only

?The idea itself is indeed good. Regarding to escaping: I think we should have it. Imagine the following example (I've took it from D73828). --- !ELF FileHeader: Class: ELFCLASS[[BITS]] Data: ELFDATA2LSB Type: ET_EXEC Machine: EM_386 # RUN: yaml2obj %s --docnum=4 -D BITS=32 -o %t-32bit.o # RUN: yaml2obj %s --docnum=4 -D BITS=64 -o %t-64bit.o Without escaping it would

Hi all, I have a new sample project set up in my llvm/projects directory, and I'd eventually like my frontend to generate an LLVM IR tree. To do so, I believe I need to link to the appropriate LLVM libraries. That's where I'm stuck. I can't seem to find any specific documentation that describes how to set up a new project to link to LLVM libraries. To get started, I added a

Hello, git bisect helped me today in tracking down a regression in LLVM/Clang. Because LLVM/Clang code is split across multiple git repositories, there were a few obstacles to overcome prior to using git bisect. I thought I would share them here, in the hope that they're useful for others. The main difficulty was to check out the version of clang and compiler-rt that would compile with a

On Mon, Aug 10, 2015 at 8:08 PM, Kostya Serebryany <kcc at google.com> wrote: > > > On Mon, Aug 10, 2015 at 5:53 PM, Brian Cain via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> >> First off, thanks -- this is a pretty great library and it feels like I'm >> learning a lot. >> > > Thanks! > > >> I'm getting some

The generic-abi thread has gone into broader subjects of the benefits and desireability of the work. I'm willing to take it as given that the encoded size of pure-relative address relocs (i.e. R_*_RELATIVE equivalents)--ultimately the RODATA segment size of a given ET_DYN file--as sole metric is a worthy goal and the ballpark savings ratios we're seeing are worth committing to a new ABI.

Hi, On Linux I observed [root at localhost poolalloc]# find . -name *.a ./Release+Asserts/lib/LLVMDataStructure.a ./Release+Asserts/lib/poolalloc.a ./Release+Asserts/lib/AssistDS.a ./Release+Asserts/lib/libpoolalloc_fl_rt.a ./Release+Asserts/lib/libpoolalloc_rt.a ./Release+Asserts/lib/libpa_pre_rt.a ./Release+Asserts/lib/libcount.a On cygwin I observed kpawar at KPAWAR-LT

Hi, I'm using LLVM 1.8 with the GCC4-frontend on a Slackware 10.2 box (GCC 3.3.6). When issuing the following command (line 14 in a script called manual.sh): llvm-ld -O1 *.trans -L${SOME_LIB_DIR} -L${SOME_OTHER_LIB_DIR} -L${LLVM_FRONT}/lib -lSOME_LIB -lSOME_OTHER_LIB -load=${MY_LIB_DIR}/opt1.so -load=${MY_LIB_DIR}/opt2.so -debug-pass=Details -debug -o test ... I get the following

Dear Nikhil, The lib/PoolAllocate code doesn't compile with LLVM mainline, and you don't need it for SAFECode. You can remove PoolAllocate from the list of directories to compile in poolalloc/lib/Makefile. Also, are you using the code from Peter's Github repository? I think Peter made this change in his code already. Regards, John Criswell On 7/29/15 11:27 AM, Nikhil Reddy

Should I expect the "-openmp" to work for this RC? I got a link error (only in phase 3?). Maybe the fact that it happened in phase 3 suggests some hardware malfunction of mine? Or are there tests executed on phase 3 that aren't attempted on earlier phases? $ CC=clang CXX=clang++ ./test-release.sh -release 3.7.1 -rc 2 -j1 -openmp -triple armv7l-ubuntu15.10-linux-gnueabihf ... cd