similar to: [LLVMdev] Xcode 4 autocomplete of LLVM includes

Jonathan Ragan-Kelley <katokop1 <at> gmail.com> writes: > > Slightly off-topic, but I imagine this crowd must have some experience > using Xcode 4 for projects linking to LLVM. I've actually started > using Xcode 4 as an IDE for C/C++ development thanks to the vastly > improved code analysis-based tools it's inherited largely thanks to > LLVM. But,

Building on OS X 10.7.1 with the standard toolchain, I have seen the following linker warnings going back a number of versions in trunk whenever I build an executable linked with LLVM: ld: warning: direct access in llvm::fouts() to global weak symbol llvm::formatted_raw_ostream::~formatted_raw_ostream() means the weak symbol cannot be overridden at runtime. This was likely caused by

After upgrading today to xcode 7, a bunch of my cmake build files stopped working, because we went from $ clang --version Apple LLVM version 6.1.0 (clang-602.0.53) (based on LLVM 3.6.0svn) to $ clang --version Apple LLVM version 7.0.0 (clang-700.0.72) See, so now anything that parsed this output to make decisions based on the underlying llvm/clang version no longer works,

On 28.12.2011, at 19:02, Jonathan Ragan-Kelley wrote: > Building on OS X 10.7.1 with the standard toolchain, I have seen the > following linker warnings going back a number of versions in trunk > whenever I build an executable linked with LLVM: > > ld: warning: direct access in llvm::fouts() to global weak > symbol llvm::formatted_raw_ostream::~formatted_raw_ostream()

Sorry if this isn't the right place; but I'm facing an XCode 4 (LLVM 2.0 to Apple, I heard it's LLVM 2.9 under the hood) issue that may involve LLVM, and maybe some people on this list could help me short-circuit the source. I have a code pattern that, when used in XCode 4 in Objective C++ files, causes the whole IDE to go crash. It is a stripped sample to highlight the issue. In

Hi, I'm currently trying to use Speex on the iPhone but have some difficulties to get Speex compiled with XCode. Unfortunately I'm very new to XCode and it would be great if someone could give me a hint what the problem is. Here is what I did in detail: 1. Downloaded the Source Code speex-1.2rc1.tar.gz from www.speex.org 2. Start Xcode 3.1.4 3. File > New Project ... 4. iPhone OS

Forgive me if I'm missing something obvious, but it seems that a number of core instructions—I'm specifically running in to `atomicrmw`, `fence`, and `cmpxchg` at the moment—cannot be constructed from the C bindings, and are therefore also inaccessible to the OCaml bindings. There are opcodes for each of these in the llvm-c/Core.h, but there seems to be no way to construct them. Is there

How soon would I need to submit a patch for this for it to have a comfortable shot at making it into the 3.2 release? On Sep 14, 2012, at 8:05 PM, Eric Christopher <echristo at apple.com> wrote: > > On Sep 14, 2012, at 4:53 PM, Jonathan Ragan-Kelley <jrk at csail.mit.edu> wrote: > >> Is there a reason these should be omitted? > > Not in particular. Things are

On May 28, 2009, at 6:03 PM, Jonathan Ragan-Kelley wrote: > In the current trunk, System/Atomic.[h,cpp] define void > llvm::sys::MemoryFence(). This conflicts with the MemoryFence macro in > <windows.h> and (since it's a preprocessor macro, and not a scoped > function definition) causes the sys::MemoryFence definition on > Atomic.cpp:23 to explode, as it's

Hi all In order to get ready for the upcoming final 9.0 release code I have now switched to the 'release/9.x' branch that I pulled from github. Unfortunately, after running cmake in the usual way, I found that many xcode schemes are missing on the resulting project. Particularly, I added -DLLVM_ENABLE_PROJECTS=clang to the terminal command line. The logs correctly state that ‘clang

I finally got around to adding these. The patch is posted in a pull request on my copy of llvm.git: https://github.com/jrk/llvm/pull/3 and a simple test with OCaml is here: https://gist.github.com/3948460 Feedback welcome. On Sep 14, 2012, at 7:53 PM, Jonathan Ragan-Kelley <jrk at csail.mit.edu> wrote: > Forgive me if I'm missing something obvious, but it seems that a >

I've been using make to build llvm but use Xcode for most other projects I work on. I decided to try running cmake to build an xcode project for llvm. The results were disappointing. The generated xcode project does not encode that executables link with static libraries. Instead, the static libraries are snuck in under "Other linker flags", then some pre- and post- scripts on

Yes, indeed. On May 28, 10:41 pm, Owen Anderson <resis... at mac.com> wrote: > > Wait, it defines MemoryFence() AND MemoryBarrier()?? > > Sheesh, they had to take all the reasonable names.  :-/

What is the current state of the JIT on Windows x64? I have noticed intermittent conversation about past incompatibility due to the calling convention idiosyncrasies, as well as some suggestion from last fall that it was targeted for a fix in the 2.5 timeframe, but see no definitive conclusion. Is this working in 2.5, in trunk, or likely to be in trunk soon?

I can't seem to find reference to intrinsics, beyond the is_intrinsic function. I am building a backend which needs to perform some target-specific code-generation (for SSE, AVX, and NEON), and intrinsics are the standard path in the C++ API.

Hi, I am trying to use the new LLVM-2.7 release in Xcode for my analysis and development. However, I do not see the top level Xcode directory as in LLVM-2.6. Can someone tell me how to develop on top of LLVM-2.7 using Xcode? Best Regards, Raj

Hi everyone.I am using Mac OS X to inspect the llvm source code. Although the make command works perfectly when compiling the source code, the Xcode tool prompted me: *Makefile:26: Makefile.config: No such file or directory* *Makefile:58: /Makefile.rules: No such file or directory* I downloaded the latest SVN code from the web site, built it without any modification in Xcode context. Xcode

The ability to archive object files generated with -flto under LLVM.org clang 3.9.0 or 4.0svn trunk is broken against the currently shipping Xcode releases including the upcoming Xcode 8.1 GM. https://llvm.org/bugs/show_bug.cgi?id=30791 $ clang-3.9 -flto -O1 -c *.i $ ar cr libtar.a paxerror.o paxexit-status.o paxnames.o rtapelib.o stdopen.o wordsplit.o xattr-at.o error: Unknown attribute kind

does somebody use XCode on Mac for RoR instead of TextMate? I wonder how is it compared to TextMate... TextMate uses the default font of Monaco... the Xcode screenshot on Wikipedia uses Courier... I wonder if Xcode looks as good as TextMate when the font is changed to Monaco as well? Thank you. -- Posted via http://www.ruby-forum.com/.

https://bugzilla.samba.org/show_bug.cgi?id=13044 Bug ID: 13044 Summary: On macOS 10.12.6 with the new Xcode 9, `make check` is full of failures Product: rsync Version: 3.1.2 Hardware: x86 OS: Mac OS X Status: NEW Severity: regression Priority: P5 Component: core