Displaying 6 results from an estimated 6 matches for "cindexcodecompletion".
2011 Oct 24
1
[LLVMdev] build warnings
...>
$ make happiness
...
Updated to revision 142790.
...
make[4]: Entering directory
`/home/ecsardu/LLVM/build-tcclab1/tools/clang/tools/libclang'
llvm[4]: Compiling CIndex.cpp for Release+Asserts build (PIC)
llvm[4]: Compiling CIndexCXX.cpp for Release+Asserts build (PIC)
llvm[4]: Compiling CIndexCodeCompletion.cpp for Release+Asserts build (PIC)
llvm[4]: Compiling CIndexDiagnostic.cpp for Release+Asserts build (PIC)
llvm[4]: Compiling CIndexHigh.cpp for Release+Asserts build (PIC)
llvm[4]: Compiling CIndexInclusionStack.cpp for Release+Asserts build (PIC)
llvm[4]: Compiling CIndexUSRs.cpp for Release+Ass...
2015 Jul 08
2
[LLVMdev] Building clang + libc++ + libc++abi
[Sorry about the crosspost. Since this is a clang build question but
the build is invoked from the top-level LLVM directory I'm not sure
where the question should go.]
I've got a clang build against libstdc++ on Linux but I would really
like one built against libc++/libc++abi. In other words I'd like to
rebuild clang/llvm with clang using libc++ and libc++abi on Linux.
I looked at
2014 Jun 03
2
[LLVMdev] llvm atomics on 64-bit values
I need an atomic pointer exchange, so I took a look at Support/Atomic.h,
and the only supported types are 32-bit values. I can't figure out an
obvious reason for this other than perhaps nobody ever had need of this
yet, but given that this is kind of a low level thing, I thought I should
ask first. Is there any reason I should not add 64-bit versions of the
atomic functions?
Additionally,
2011 Oct 23
0
[LLVMdev] build warnings
Hi,
I haven't seen those errors. Clang and LLVM both build with no warnings on the 3 versions of GCC I test with. MSVC reports loads of warnings however.
Cheers,
James
________________________________________
From: Csaba Raduly [rcsaba at gmail.com]
Sent: 23 October 2011 18:44
To: James Molloy
Cc: Paul Berube; llvmdev at cs.uiuc.edu
Subject: Re: [LLVMdev] build warnings
On Sat, Oct 22,
2015 Jul 08
2
[LLVMdev] [cfe-dev] Building clang + libc++ + libc++abi
...s
> -Wl,-z,defs -shared -Wl,-soname,libclang.so.3.7 -o
> ../../../../lib/libclang.so.3.7 CMakeFiles/libclang.dir/ARCMigrate.cpp.o
> CMakeFiles/libclang.dir/BuildSystem.cpp.o
> CMakeFiles/libclang.dir/CIndex.cpp.o
> CMakeFiles/libclang.dir/CIndexCXX.cpp.o
> CMakeFiles/libclang.dir/CIndexCodeCompletion.cpp.o
> CMakeFiles/libclang.dir/CIndexDiagnostic.cpp.o
> CMakeFiles/libclang.dir/CIndexHigh.cpp.o
> CMakeFiles/libclang.dir/CIndexInclusionStack.cpp.o CMakeFiles/libclang.!
> dir/CIndexUSRs.cpp.o CMakeFiles/libclang.dir/CIndexer.cpp.o
> CMakeFiles/libclang.dir/CXComment.cpp.o
> C...
2011 Oct 23
5
[LLVMdev] build warnings
On Sat, Oct 22, 2011 at 12:24 AM, James Molloy wrote:
> Hi Paul,
>
> That should be easy enough, because the LLVM build has no warnings in it!
>
> Some of us build with -Werror, and even with those of us that don't warnings are not tolerated. You're already seeing all the warnings that are coming out of the build :)
So, all the "variable might be used