similar to: [LLVMdev] Question about linking llvm-mc when porting a new backend

Hello all, I am a LLVM newer who want to add a new backend(EBC) into LLVM. After coping the related files from another target and modifying it, I meet a problem when I build the project. The error message is as follows: ================================================================ [ 94%] Built target llvm-dis Linking CXX executable ../../bin/llvm-mc Undefined symbols:

Just ran into this as well. Did you ever open a a bug report about it? On Tue, Jun 18, 2013 at 3:43 AM, Alessio Giovanni Baroni < alessiogiovanni.baroni at gmail.com> wrote: > Here there is the dump: > > SelectionDAG.cpp:81: static bool > llvm::ConstantFPSDNode::isValueValidForType(llvm::EVT, const llvm::APFloat > &): Assertion `VT.isFloatingPoint() && "Can

I don't. 2013/6/29 Keno Fischer <kfischer at college.harvard.edu> > Just ran into this as well. Did you ever open a a bug report about it? > > > On Tue, Jun 18, 2013 at 3:43 AM, Alessio Giovanni Baroni < > alessiogiovanni.baroni at gmail.com> wrote: > >> Here there is the dump: >> >> SelectionDAG.cpp:81: static bool >>

Here there is the dump: SelectionDAG.cpp:81: static bool llvm::ConstantFPSDNode::isValueValidForType(llvm::EVT, const llvm::APFloat &): Assertion `VT.isFloatingPoint() && "Can only convert between FP types"' failed. 0 libLLVMSupport.so 0x00007f7405022de5 llvm::sys::PrintStackTrace(_IO_FILE*) + 37 1 libLLVMSupport.so 0x00007f74050232e3 2 libpthread.so.0

Dear All, Has anyone else noticed the following problem building LLVM on Mac OS X: find-cycles.pl: Circular dependency between *.a files: find-cycles.pl: libLLVMAsmPrinter.a libLLVMCodeGen.a libLLVMSelectionDAG.a llvm[1]: Building llvm-config script. cat: /Users/criswell/box/x86/llvm22/tools/llvm-config/FinalLibDeps.txt: No such file or directory -- John T.

John Criswell wrote: > Dear All, > > Has anyone else noticed the following problem building LLVM on Mac OS X: > > find-cycles.pl: Circular dependency between *.a files: > find-cycles.pl: libLLVMAsmPrinter.a libLLVMCodeGen.a libLLVMSelectionDAG.a > llvm[1]: Building llvm-config script. > cat: /Users/criswell/box/x86/llvm22/tools/llvm-config/FinalLibDeps.txt: > No such

On Apr 14, 2009, at 8:53 AMPDT, John Criswell wrote: > John Criswell wrote: >> Dear All, >> >> Has anyone else noticed the following problem building LLVM on Mac >> OS X: >> >> find-cycles.pl: Circular dependency between *.a files: >> find-cycles.pl: libLLVMAsmPrinter.a libLLVMCodeGen.a >> libLLVMSelectionDAG.a >> llvm[1]: Building

$ make update ...snip... Updated to revision 69967. $ ENABLE_OPTIMIZED=1 make ...snip... llvm[1]: Regenerating LibDeps.txt.tmp llvm[1]: Checking for cyclic dependencies between LLVM libraries. find-cycles.pl: Circular dependency between *.a files: find-cycles.pl: libLLVMAsmPrinter.a libLLVMCodeGen.a libLLVMSelectionDAG.a llvm[1]: Building llvm-config script. cat:

Hi, I am currently working on a more or less intrusive patch (D37896), which pulls optimizations on multiplications from some back-ends, e.g., (mul x, 2^N + 1) => (add (shl x, N), x) in AArch64, into the DAGCombiner to have this optimization generic on all targets. However, running the LLVM Tests leads to 67 unexpected results. Am 19.09.2017 um 15:58 schrieb Sanjay Patel: > For the

Hey, So in Fedora rawhide we are now building llvm 3.7.1 into the lots of little shared libraries format. However I'm running into a major problem with the fact that sometimes dlclose isn't dropping all the LLVM libraries from the address space of the process. We have a sequence like this: a) X server asks mesa gbm library to init, it loads the kms_swrast_dri.so with

Hello, I am building LLVM with ninja on Linux environment and I continue to have the error below. I am thinking that the cause might be my PC not having sufficient RAM memory. In this sense, I extended my swap memory with a swap file (90GB), but it didn't solved the problem. Should I add more physical RAM memory to my PC, or is there any software based solution I can try first? Thank you and

Hi Craig, protecting the transformation with: if (TLI.isTypeLegal(VT) && TLI.isOperationLegal(ISD::SUB, VT) && TLI.isOperationLegal(ISD::ADD, VT) && TLI.isOperationLegal(ISD::SHL, VT) && TLI.isOperationLegal(ISD::SRA, VT)) { shows the same result. Michael On 22.09.2017 07:19, Craig Topper wrote: > Is VT a legal type on Hexagon?

Hi, I wondered whether the AggressiveAntiDepBreaker can properly handle predicated instructions. At the end of PrescanInstruction the "DefIndices" array is updated with the destination register without checking whether the instruction is predicated. That shortens the live range: Later on, in HandleLastUse we check whether the register IsLive, which considers only

Hi, Try these scripts to build llvm and llvm-gcc. It's the ones I use and I managed to get them to work when I saw another build script using those CFLAGS. They compile llvm and stuff using only x86_64, but you can then generate code for i386 (just use a different backend). The configuration options are at the top of the scripts and they install llvm and llvm-gcc to ~/llvm. Regards,

Hi Sanjay, thanks for this information. I did get a little bit further with the patch. However, Hexagon gives me headaches. I tried to limit the scope of the patch to the BeforeLegalizeTypes phase and Hexagon still reaches the unreachable. Hexagon tries to split or widen a vector type for a node with custom lowering where the unreachable arises from inside TargetLowering::ReplaceNodeResults

On Sat, Jun 5, 2010 at 3:18 AM, Duncan Sands <baldrick at free.fr> wrote: > Hi Tom, > > I'm pretty sure that the LLVMContext constructor is defined in libLLVMCore.a > What is the output of `llvm-config --libs bitwriter`?  Does it include > -lLLVMCore? Hi Duncan, e0082888 at e0082888-laptop:~$ local/bin/llvm-config --libs bitwriter -lLLVMBitWriter -lLLVMCore -lLLVMSupport

Is VT a legal type on Hexagon? It looks like Hexagon may be setting SHL as Custom for every defined vector type. Try adding TLI.isTypeLegal(VT) too. ~Craig On Thu, Sep 21, 2017 at 10:06 PM, Haidl, Michael < michael.haidl at uni-muenster.de> wrote: > Hi Sanjay, > > thanks for this information. I did get a little bit further with the > patch. However, Hexagon gives me headaches.

Hi all, I am trying to compile with a minimal TestAsmParser class, but I get the following error. ---------------- [43/780] Linking CXX executable bin/llvm-mc FAILED: : && /usr/bin/c++ -fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wno-maybe-uninitialized -Wno-comment -std=c++11

There are multiple problems/questions here: 1. Make sure you've updated trunk to the latest rev before running update_llc_test_checks.py on lea-3.ll. Ie, I would only expect the output you're seeing if you're running the script on a version of that test file before r313631. After that commit, each RUN has its own check prefix, so there should be no conflict opportunity. 2. I

I've run into a problem with the ocaml bindings and the jit. It builds fine without the jit, but when I try to include it it tries to use the c object files from the build location, instead of the install location: > llvm-config --libdir --libfiles engine /opt/local/lib /opt/local/lib/LLVMX86.o /opt/local/lib/libLLVMSelectionDAG.a /opt/local/lib/libLLVMCodeGen.a