search for: armdagtodagisel

...bort.c:91:0 #7 0x00000000043abcc4 bindingsErrorHandler(void*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool) /home/nancy/rpp_llvm/llvm-project/llvm/lib/Support/ErrorHandling.cpp:231:0 #8 0x0000000002db244e (anonymous namespace)::ARMDAGToDAGISel::SelectVLDSTLane(llvm::SDNode*, bool, bool, unsigned int, unsigned short const*, unsigned short const*) /home/nancy/rpp_llvm/llvm-project/llvm/lib/Target/ARM/ARMISelDAGToDAG.cpp:2074:0 #9 0x0000000002dbc3ad (anonymous namespace)::ARMDAGToDAGISel::Select(llvm::SDNode*) /home/nancy/rpp_llvm/llvm-pro...

Dear list, git checkout llvmorg-8.0.0 -b llvm8.0 cmake -G "Unix Makefiles" ../llvm-project/llvm -DCMAKE_BUILD_TYPE=Debug -DLLVM_ENABLE_PROJECTS="clang;lld" -DLLVM_TARGETS_TO_BUILD="X86;NVPTX;AMDGPU;ARM;AArch64" [arm.cpp] #define vst4_lane_f16(__p0, __p1, __p2) __extension__ ({ \ float16x4x4_t __s1 = __p1; \ __builtin_neon_vst4_lane_v(__p0, __s1.val[0],

Hi, I got that message from a call to InstrEmitter::AddOperand. I am writing a back end for CortexM0 (for self teaching purposes), I am working on LDR with immediate offset instruction. In the ARM backend, if the offset is 0, the following code is executed by the function ARMDAGToDAGISel::SelectThumbAddrModeImm5S Base = N.getOperand(0); OffImm = CurDAG->getTargetConstant(0, MVT::i32); If I do a similar thing in my backend, I get this assertion message. I found out that if I execute the code below, the problem disappear. Base = N; OffImm = CurDAG->getTargetConstant(0, TM...

Hi All, I started to work on code-size improvements on ARM target by comparing GCC and LLVM generated code. My first candidate was switch-case lowering. I also created a Bugzilla issue for this topic: https://bugs.llvm.org/show_bug.cgi?id=34902 The full example code and the generated assembly for GCC and for LLVM is in the Bugzilla issue. My first idea was to simplify the following

...ing. Thus I believe the safest solution is to always force 64-bit operands into even/odd pairs for any inline asm. In other words, we should probably do something like this (untested): --- a/lib/Target/ARM/ARMISelDAGToDAG.cpp +++ b/lib/Target/ARM/ARMISelDAGToDAG.cpp @@ -3457,19 +3457,6 @@ SDNode *ARMDAGToDAGISel::SelectInlineAsm(SDNode *N){ bool Changed = false; unsigned NumOps = N->getNumOperands(); - ExternalSymbolSDNode *S = dyn_cast<ExternalSymbolSDNode>( - N->getOperand(InlineAsm::Op_AsmString)); - StringRef AsmString = StringRef(S->getSymbol()); - - // Normally, i64 dat...

...ing. Thus I believe the safest solution is to always force 64-bit operands into even/odd pairs for any inline asm. In other words, we should probably do something like this (untested): --- a/lib/Target/ARM/ARMISelDAGToDAG.cpp +++ b/lib/Target/ARM/ARMISelDAGToDAG.cpp @@ -3457,19 +3457,6 @@ SDNode *ARMDAGToDAGISel::SelectInlineAsm(SDNode *N){ bool Changed = false; unsigned NumOps = N->getNumOperands(); - ExternalSymbolSDNode *S = dyn_cast<ExternalSymbolSDNode>( - N->getOperand(InlineAsm::Op_AsmString)); - StringRef AsmString = StringRef(S->getSymbol()); - - // Normally, i64 dat...

...0x000000010fe15779 llvm::SelectionDAGISel::SelectAllBasicBlocks(llvm::Function const&) + 1029 6 llc 0x000000010fe14ac7 llvm::SelectionDAGISel::runOnMachineFunction(llvm::MachineFunction&) + 1521 7 llc 0x000000010f1b56d4 (anonymous namespace)::ARMDAGToDAGISel::runOnMachineFunction(llvm::MachineFunction&) + 20 8 llc 0x000000010f9b7914 llvm::MachineFunctionPass::runOnFunction(llvm::Function&) + 114 9 llc 0x000000010fb357e6 llvm::FPPassManager::runOnFunction(llvm::Function&) + 294 10 llc...

Hi Moritz, On 26 September 2017 at 09:09, Moritz Angermann via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I’ve run into a case where `llc -mattr=+soft-float` for > "armv7-unknown-linux-androideabi” segfaults, while > `llc -float-abi=soft` does not. Similarly if the > "target-features"="+soft-float” metadata is embedded, > llc segfaults. The float-abi

Hi, I’ve run into a case where `llc -mattr=+soft-float` for "armv7-unknown-linux-androideabi” segfaults, while `llc -float-abi=soft` does not. Similarly if the "target-features"="+soft-float” metadata is embedded, llc segfaults. I fear I’m missing something rather subtle here, could someone help me understand the differences? Cheers, Moritz

...0x0000000001c13b86 llvm::SelectionDAGISel::SelectAllBasicBlocks(llvm::Function const&) (llvm.inst/bin/clang+++0x1c13b86) #7 0x0000000001c10140 llvm::SelectionDAGISel::runOnMachineFunction(llvm::MachineFunction&) (llvm.inst/bin/clang+++0x1c10140) #8 0x000000000083e7a1 (anonymous namespace)::ARMDAGToDAGISel::runOnMachineFunction(llvm::MachineFunction&) (llvm.inst/bin/clang+++0x83e7a1) #9 0x0000000000cdee22 llvm::MachineFunctionPass::runOnFunction(llvm::Function&) (llvm.inst/bin/clang+++0xcdee22) #10 0x0000000000fa55f4 llvm::FPPassManager::runOnFunction(llvm::Function&) (llvm.inst/bin/clang...

...but-set-variable] /home/greened/src/llvm-30-rc3/llvm/lib/CodeGen/SelectionDAG/LegalizeDAG.cpp:1632:15: warning: variable ‘WideScalarVT’ set but not used [-Wunused-but-set-variable] /home/greened/src/llvm-30-rc3/llvm/lib/Target/ARM/ARMISelDAGToDAG.cpp: In member function ‘llvm::SDNode* {anonymous}::ARMDAGToDAGISel::SelectABSOp(llvm::SDNode*)’: /home/greened/src/llvm-30-rc3/llvm/lib/Target/ARM/ARMISelDAGToDAG.cpp:2319:12: warning: variable ‘DL’ set but not used [-Wunused-but-set-variable] /home/greened/src/llvm-30-rc3/llvm/lib/Target/ARM/AsmParser/ARMAsmParser.cpp: In member function ‘bool {anonymous}::ARMAs...

On 7 November 2011 22:00, Bill Wendling <wendling at apple.com> wrote: > We are starting on our third (and hopefully last) round of testing for LLVM 3.0. Please visit: > >        http://llvm.org/pre-releases/3.0/rc3/ > > for the sources. There are also binaries for Darwin up there, with more to come during the week. Please build this release candidate, test it out on your

Good day, LLVMers! We are starting on our third (and hopefully last) round of testing for LLVM 3.0. Please visit: http://llvm.org/pre-releases/3.0/rc3/ for the sources. There are also binaries for Darwin up there, with more to come during the week. Please build this release candidate, test it out on your projects, and let us know if you find any regressions from the 2.9 release. Please keep