similar to: [LLVMdev] xcodebuild and LLVM

On Sep 3, 2008, at 3:12 PM, John Criswell wrote: > Dear All, > > Is there a way to convince xcodebuild to build bitcode files for LLVM > for an arbitrary Xcode project? So far, I've been able to get > xcodebuild to use LLVM by installing XCode 3.1 and using CC="llvm-gcc" > on the command line. I've also managed to get LLVM bitcode generates > for

Dear Ted and All, Thanks. This has helped some. However, I'm now getting errors from libtool about an object being modified after free. Is libtool supposed to work with LLVM bitcode files? If so, would grabbing the latest source potentially fix the problem (I'm currently using XCode 3.1), or will I need a way to convince xcodebuild to use something other than libtool? -- John T.

Hi John, I'm not certain if libtool works with LLVM bitcode files, and I don't think that all of the tools that manipulate/inspect object files on Mac OS X understand bitcode files either. I suspect that this will change over time. I believe that Devang and others who implemented LTO on Mac OS X can probably provide you with specific details of tool support for bitcode files.

On Sep 3, 2008, at 3:12 PM, John Criswell wrote: > Is there a way to convince xcodebuild to build bitcode files for LLVM > for an arbitrary Xcode project? So far, I've been able to get > xcodebuild to use LLVM by installing XCode 3.1 and using CC="llvm-gcc" > on the command line. I've also managed to get LLVM bitcode generates > for intermediate files by using

On Sep 11, 2008, at 9:30 PM, Ted Kremenek wrote: > Hi John, > > I'm not certain if libtool works with LLVM bitcode files, and I don't > think that all of the tools that manipulate/inspect object files on > Mac OS X understand bitcode files either. Yes. Right now only ld recognizes LLVM bitcode files. > I suspect that this will > change over time. Yes. - Devang

Hi Joan, On Fri, 14 Jun 2019 at 11:45, Joan Lluch <joan.lluch at icloud.com> wrote: > When I started with this, I just downloaded the sources for the LLVM site, I did not even created a git for it. Then ran the CMAKE app (not from the command line) with the default settings other than also adding the ‘experimental’ targets, and boom a fully functional XCode project was created, so I gave

On 2010-07-21, at 2:24 AM, Brian Willoughby <brianw at sounds.wa.com> wrote: > The flac sources are distributed in a configuration that is designed > primarily for building from the command-line. I seem to recall that > there might have been an Xcode project in there at some point, but > if there was, it never worked well. In all honesty, I may be > getting

Hi, I configured and built LLVM as follows on Mac OS 10.13.2: $ pwd <llvm-build-dir> $ cmake -G "Xcode" -DCMAKE_INSTALL_PREFIX=<llvm-install-dir> -DLLVM_ENABLE_PIC=0 <llvm-src-dir>/llvm $ xcodebuild -project LLVM.xcodeproj All binaries are in <llvm-build-dir>/Debug/bin. I am interested in using the output of llvm-config. Now, when I run $

Thanks for your reply, Paul. That seems to be a plausible explanation. I ended up adding code in my project to massage the output of llvm-config to the right paths based of the values of CMAKE_GENERATOR and build-mode. Bharadwaj On Dec 15, 2017 9:46 AM, "Robinson, Paul" <paul.robinson at sony.com> wrote: It may be that llvm-config simply doesn't understand a

Downloaded Xcode 4.3 for Lion from the app store, and am following the tutorial for installing wine: http://www.davidbaumgold.com/tutorials/wine-mac/ When I get to part 3 and it tells me to type the following code into terminal Code: $ sudo port install wine I get the following message: Code: xxx-xxx-macbook-pro:~ Kaoss$ sudo port install wine Password: Warning: xcodebuild exists but

Please, can anybody show me the required steps for running the LLVM regression tests, or point me to a detailed doc? I read the available documentation in https://llvm.org/docs/TestingGuide.html <https://llvm.org/docs/TestingGuide.html> but that's mostly a general description on what’s available rather than an “guide”. This is what I tried: - Installed both LLVM and CLANG using

On Nov 25, 2012, at 6:49 PM, Eli Friedman <eli.friedman at gmail.com> wrote: > On Sun, Nov 25, 2012 at 3:19 PM, Joe Abbey <jabbey at arxan.com> wrote: >> If cmake happens to detect GCC for the C compiler and Clang for the C++ >> compiler, then a manual override of either the C compiler or >> SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG is required. This has been

Hello everyone, I'm not sure whether this is the best place to send the question, but since I'm mostly interested in FLAC and there didn't appear to be a better place for it.. here goes. I pulled the latest source code from the SVN repo along with all the external dependencies including FLAC. I've been able to compile the FLAC.framework file using the 10.5 SDK in Xcode 3.2 with a

Are you building llvm-gcc yourself? If so, what version? Xcode releases include an older llvm-gcc and libLTO.dylib, which may not understand bitcode generated by newer self-built compilers. If you are only using llvm-gcc from the Xcode tools release, use the driver from: /Developer/usr/bin/llvm-gcc-4.2 If you are building llvm-gcc yourself, try, in this order: 1) sudo ln -s

Shantonu Sen wrote: > Are you building llvm-gcc yourself? If so, what version? > > Xcode releases include an older llvm-gcc and libLTO.dylib, which may not understand bitcode generated by newer self-built compilers. > Thanks. A bitcode format mismatch was the problem. I'm not sure if the problem stems from the fact that the bitcode was generated for the wrong architecture

Yes, that’s right. Some LLVM terminology though: The blocks you mention, are called the “exiting blocks” of the loop, and the blocks outside the loop (that are the targets of these exiting blocks) are called the exit blocks. getExitingBlocks in LoopInfoImpl.h is the code you’re interested in. By definition: one of the successor’s of the exiting block is an exit block, and it should have another

I’m developing a Common Lisp compiler for OS X and Linux that uses LLVM as its backend and interoperates with C++. It’s at: github.com/drmeister/clang I need to compile one C++ source file containing small, intrinsic functions into an LLVM-IR bitcode file and link it with bitcode generated by my compiler running LLVM3.6.1. I have been unable to do this for more than a year and I was hoping

I'm confused. libLTO takes bitcode files as input and creates a native object file as output. Why would libLTO create bitcode as output? If so, you're changing the existing API contract. Or are you creating an out-of-band bitcode file, in which case the linker would never see it. ld doesn't have bitcode support, it has libLTO support, and libLTO is what processes the bitcode.

Hi Tobias The problem is that your static archive has a SYMDEF that is empty, so linker thinks the static library provided doesn't contain any symbol. The reason for that is you are using the `ranlib` from Xcode, which is too old to understand the new bitcode object files produced by llvm 10. There are lots of ways to fix that: * The standard way to create static library on macOS is to use

On Tue Nov 04 2014 at 12:43:05 PM Peter S. Housel <housel at acm.org> wrote: > On 11/04/2014 07:04 AM, Robinson, Paul wrote: > >> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Sean Silva > >> > >> You haven't established that you really need this. AFAIK Apple's linker > >> doesn't need this