similar to: Problems trying to build LLVM

On Fri, Aug 04, 2017 at 01:54:33PM -0600, Jonathan Roelofs wrote: > > > On 8/4/17 1:14 PM, Goran Mekić via llvm-dev wrote: > > On Thu, Aug 03, 2017 at 08:22:24AM -0600, Jonathan Roelofs wrote: > > > IIUC, you don't want to cross compile llvm itself (which is what those > > > instructions are for), but instead you want to *use* llvm to cross compile > >

On Fri, Aug 04, 2017 at 04:03:35PM -0600, Jonathan Roelofs wrote: > > > 1) Pick a directory as your sysroot > > ~/arm-sysroot > > > > > 2) Install the libc headers there (without having built it) > > What I did was mv musl-*/include ~/arm-sysroot/usr/include. > > I think you need to copy them, not move them. On a new directories and fresh untar of musl, I

Hi, all, I am planning to add clang-tidy checkers for my company. How to add a new module for my company? Please help, thanks in advance. I try to copy files from cert module, and rename cert to Misra, then add a rule named "m-0-1-1" by ./add_new_checker.py. then I run ninja check-clang-tool, but my case is failed due to below error Running ['clang-tidy',

On Thu, Aug 03, 2017 at 08:22:24AM -0600, Jonathan Roelofs wrote: > IIUC, you don't want to cross compile llvm itself (which is what those > instructions are for), but instead you want to *use* llvm to cross compile > things. > > To build your sysroot, you'll need to cross-build: > > 1) A libc. Good choices for that for baremetal are: newlib or musl. > 2)

I'm going through the Kaleidoscope tutorial, adding the codegen() functions: https://llvm.org/docs/tutorial/LangImpl03.html. I cannot find any discussion of header files to include, (other than the include of llvm/ADT/STLExtras.h in the lexer/parser code), and the compilation is failing due to several undefined symbols: LogErrorV, Value, LLVMContext, APFloat, and others. I've been hunting

I configured with this command: " cmake ../llvm -G"Visual Studio 16 2019" -A Win32 -Thost=x64 -DLLVM_ENABLE_EH=ON -DCMAKE_BUILD_TYPE=Release -DLLVM_USE_CRT_RELEASE=MT -DLLVM_ENABLE_RTTI=ON -DLLVM_ENABLE_PROJECTS="clang;clang-tools-extra;lld;libcxx;libcxxabi" -DCMAKE_CXX_FLAGS="/permissive- /D_SILENCE_ALL_CXX17_DEPRECATION_WARNINGS" -DCMAKE_CXX_STANDARD=17 "

I hope I'm not being too presumptuous or anything when I say this: could you guys please review the obj.ClangAST.vcxproj project and try to fix the ambiguity error? Reid asked me why I'm using C++17. I just want to use the latest released standard. Most if it still compiles anyway. So I'll stick with it. -------------- next part -------------- An HTML attachment was scrubbed...

> On Nov 16, 2016, at 12:05 PM, Jonathan Roelofs <jonathan at codesourcery.com> wrote: > > > > On 11/16/16 11:48 AM, Mehdi Amini via llvm-dev wrote: >> Hi all, >> >> An issue that come up from time to time and has cost hours for debug for >> many of us and users of LLVM is that an assert build isn’t ABI >> compatible with a release build.

Hi, when using the "Debug" build of LLVM 8.0 my application which uses the LLVM builder and MCJIT components fails at startup with: symbol lookup error: ./main: undefined symbol: _ZN4llvm23EnableABIBreakingChecksE (unmangled: llvm::EnableABIBreakingChecks) The application works fine with the "Release" build of LLVM 8.0! (Right now, I need the Debug build for access to

Hi, I am very excited to take the awesome tutorial of implementing *Kaleidoscope*. But I got stuck here... I have done the AST parsing, however, when I introduce these 'llvm/IR/*' headers, I got a compiling error... But if I delete these headers it runs well ... """headers #include "llvm/IR/BasicBlock.h" #include "llvm/IR/Constants.h" #include

My problem is that the .td and .h files are not shown as sources in the codeblocks (.cbp) output generated by cmake. I’m consuming the .cbp file with Qt Creator - it’s seems to be an otherwise excellent tool for llvm development. It seems that the culprit is llvm_process_sources function in cmake/modules/LLVMProcessSources.cmake. The addition of .td sources and header files is wrapped in the

Hi all, An issue that come up from time to time and has cost hours for debug for many of us and users of LLVM is that an assert build isn’t ABI compatible with a release build. The CMake flags that controls this behavior is LLVM_ABI_BREAKING_CHECKS ( LLVM_ABI_BREAKING_CHECKS:STRING Used to decide if LLVM should be built with ABI breaking checks or not. Allowed values are WITH_ASSERTS (default),

Hi All: I'm running Mandrake 8.1 (downloaded) and the install went fine. Configuring Samba however is another story. I get the message "could not connect to host - localhost" on the Linux box. I cannot see the network from the Linux system. The Linux system is visable from Win'98SE as are the shares but I cannot access them "password is incorrect". This does not

I was wondering if there is an answer to this challenge or if I just have to live with it? I'm a bit of a Newbie here. I'm in the process of setting up Samba -2.2.2 on a Redhat v7.1 (Seawolf) server. I've discovered that joining the NT Domain is a simple matter of smbpasswd -j DOMAIN_NAME smbpasswd picks up the PDC name from smb.conf and moves right along. There is no need to

I decided to start playing around with building my own programming language recently, and to use LLVM to handle the assembly-level details. I'm on Kubuntu 18.04, and I started out using LLVM 6.0 from Kubuntu's packages. I put together code for dealing with my language, then went over the Kaleidoscope tutorials (which have been extremely helpful btw!). I was able to successfully get my

Hi Guys, Please look at this when making after configuring on SLES9 make: *** No rule to make target `modules/vfs_afsacl.po', needed by `bin/afsacl.so'. Stop. samba-3.0.28/source ./configure --with-smbmount --with-cifsmount --with-acl-support --with-winbind --with-vfs-afsacl --with-quotas --with-ldap this is the only other reference I have to it.. :|

On Thu, 2008-03-27 at 09:51 -0600, John Regehr wrote: > Hey, you need to be careful with this reasoning or else you'll end up > implementing a whole new language, compiler, and OS. > > Oh wait nevermind :). Don't forget prover. :-) shap

Hello all, thanks for the feedback! It sounds like you are planning to follow the approach of Joshi, Nelson and > Randall ("Denali: A Goal-directed Superoptimizer") in that you don't intend > to exhaustively enumerate all possible code sequences, and see if they are > the same as the original only better; but instead start from the original > code > sequence and

Dear LLVMers, This email is intended for those interested in path-sensitive analysis, integer overflow analysis, static analysis, and (perhaps) loop invariant computation. Traditionally, such analyses have been considered too expensive to be practical, and were mostly an academic curiosity. The core of the problem is the lack of adequate automated decision procedures which could quickly

With reference to the following thread: http://lists.llvm.org/pipermail/llvm-dev/2016-January/094100.html I am having the same issue. First I did a git pull of all the relevant directories and then doing a cmake: cmake -DLLVM_ENABLE_DOXYGEN=ON -DLLVM_ENABLE_WERROR=OFF -DLLVM_TARGETS_TO_BUILD="X86" ../llvm and followed by make: [ 22%] Built target LLVMVectorize [ 25%] Built target