llvm

I have little example code in C++: struct RecordTest { int value1; int value2; }; void test() { RecordTest rt; rt.value1 = 15; rt.value2 = 75; } and LLVM 3.4 IR for it: %struct.RecordTest = type { i32, i32 } ; Function Attrs: nounwind define void @_Z4testv() #0 { entry: %rt = alloca %struct.RecordTest, align 4 %value1 = getelementptr inbounds %struct.RecordTest* %rt, i32 0, i32 0 store i32 15, i32* %value1, align 4 %value2 = getelementptr inbounds %struct.RecordTest* %rt, i32 0, i32 1 store i32 75, i32* %value2, align 4 ret void } and a pretty easy question: How can I access to RecordTest

Regarding this technical Q&A from Apple: http://developer.apple.com/library/mac/#qa/qa1490/_index.html I think the compiler could mark calls to methods defined in categories at compile-time (it knows that they were defined in a category and not the main class because the prototype was in an @interface Class (Category) section) - so it could build a table in the object files of "external category methods". Then the linker, after doing its normal linking, should be able to concatenate/merge and process the "external category methods" tables from all objects and look for matching symbols in

In Linux, and specifically on Debian or Ubuntu, there are pre-packaged Mingw cross compilers which can generate Windows EXEs. But is there a similar cross compiler using Clang instead of GCC? (Or instructions on how to build such a beast.) I've written a tool with which you can compile easily with clang for windows on linux. Check out: https://github.com/tpoechtrager/wclang . 来源： https://stackoverflow.com/questions/12704537/is-there-a-clang-mingw-cross-compiler-for-linux

I've written a standard Analysis pass in LLVM, by extending the FunctionPass class. Everything seems to make sense. Now what I'd like to do is write a couple of intermodular passes, that is, passes that allows me to analyze more than one module at a time. The purpose of one such pass is to construct a call graph of the entire application. The purpose of the other such pass is that I have an idea for an optimization involving function calls and their parameters. I know about interprocedural passes in LLVM, via extending the ModulePass class, but that only allows analysis within a single module.

Why exactly is it that when I create an iOS static library project or framework project in Xcode, I don't need to link any iOS SDK frameworks to the project in order to make use of their headers and objects -- for example, I can #import <AudioToolbox/AudioToolbox.h> and put AudioToolbox code in the static library or framework without actually having AudioToolbox added under "Link Binary with Libraries" in build settings or having it present in the file navigator, and the project will build without issue, something that wouldn't work in an app project -- but when a developer then uses the

How to cross-compile clang/llvm for iOS? I need to get libclang (.a or .dylib i believe) to use it via C API in my iOS app. # Get LLVM/Clang mkdir llvm curl -O http://llvm.org/releases/3.4/llvm-3.4.src.tar.gz tar xzfv llvm-3.4.src.tar.gz cd llvm-3.4/tools/ curl -O http://llvm.org/releases/3.4/clang-3.4.src.tar.gz tar xzfv clang-3.4.src.tar.gz mv clang-3.4 clang cd .. # Assuming Xcode 5.1 (LLVM 3.5+ requires -stdlib=libc++ as well) export CC="clang -arch armv7 -mios-version-min=5.0 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS7.1.sdk"

I need to convert x86 assembly source code to LLVM human-readable .ll file (aka LLVM assembly language). How can I do this? If there is no direct solution would it be possible to implement one within the LLVM infrastructure with as less efforts as possible? I guess, the solution I'm looking for should be some kind of llc 's counterpart that converts .s file back to .ll representation. bsa2000 Just for those who are still seeking for more information on this topic, I want to share the information about one ongoing project ( http://dslab.epfl.ch/proj/s2e ) that I've found on the web. The project

I'm seeking clarification of what the best build options are for LLVM 3.2 on Raspbian I've fetched the LLVM source of 3.2, and my config is: cd llvm-3.2.src ./configure --build=armv6-unknown-linux-gnueabi \ --host=armv6-unknown-linux-gnueabi \ --target=armv6-unknown-linux-gnueabi --with-cpu=arm1176jzf-s \ --with-float=hard --with-abi=aapcs-vfp --with-fpu=neon \ --enable-targets=arm --enable-optimized --enable-assertions make REQUIRES_RTTI=1 sudo make install I've heard it takes quite a number of hours to build. It's been running a few hours now, happy to just let it run though. It's a long