similar to: [LLVMdev] Fwd: [windows) how to use weak references with llvm 3.4 and windows?

Thanks for your clear answer. Do you know what modifier should I use to declare such weak symbols in my llvm intermediate code? So that it can be compiled to the .o file with the weak attribute ? Le 10 févr. 2014 19:44, "Reid Kleckner" <rnk at google.com> a écrit : > COFF doesn't support the same kind of concept of 'weak' that ELF does. > This is the issue that

So instead of using linkagetypes.weak I should use externalweaklinkage ? Le 11 févr. 2014 18:29, "Reid Kleckner" <rnk at google.com> a écrit : > You'd have to use extern_weak linkage. Clang compiles the foo declaration > to: > $ clang -cc1 -emit-llvm -o - t.c | grep declare.*@foo > declare extern_weak i32 @foo(...) #1 > > > > On Tue, Feb 11, 2014 at

Yep, quite right, Evan. Any regalloc differences due to that patch are purely coincidence; -Jim > On Jun 16, 2014, at 10:13 AM, Evan Cheng <evan.cheng at apple.com> wrote: > > Hi Niklas, > > The attached patch has nothing to do with register allocation. r206094 changes how cpu auto-detection is done. I believe it's now the responsibility of the tools (e.g. llc) to

I think we have located the revision which fixes this regression: r206094 (or commit 6bb00df in llvm-mirror on GitHub). I have attached a patch which can be applied to the current release_34 branch (tested against the release_34 branch in llvm-mirror). With this patch the attached reg-alloc-test.ll file doesn't fail with the "LLVM ERROR: ran out of registers during register

Hello guys, I'm using llvm 3.3 on windows with mingw (triple: "i386-unknown-mingw32") to compile IR code that my program generates. I do it in two phases: first I emit assembly code and then assemble it. TargetMachine targetMachine = target.createTargetMachine(triple); targetMachine.setAsmVerbosityDefault(true); targetMachine.setFunctionSections(true);

Hi, The RoboVM project recently upgraded from LLVM 3.3 to 3.4 and with the new version we are sometimes seeing "ran out of registers during register allocation" errors when targeting x86 32-bit that we haven't seen before. Nothing has changed in our bitcode generator. I have attached an IR file which can be used to reproduce this problem. The problem occurs with -O2 and

I can confirm that this regression has been fixed in trunk. Should I report this as a bug in 3.4? On Thu, Apr 24, 2014 at 10:17 PM, Quentin Colombet <qcolombet at apple.com>wrote: > Hi Niklas, > > This works for me with trunk r207129. > > We did fix some register allocation issues recently, don’t know which > change fixes the issue though. > > Thanks, > -Quentin

I recently subscribed to the LLVM and Clang developer mailing lists, and earlier today read a message requesting advice on "Contributing to LLVM Projects". I'm hoping to eventually get involved as well, but with my situation being very different to that described in the referenced thread I got the idea of solliciting advice seperately. If this is not the right place to ask, though,