search for: arcmigrate

Displaying 6 results from an estimated 6 matches for "arcmigrate".

builds are failing
2020 Aug 30
2
builds are failing
Without seeing more details it's impossible to tell, but it might have been me. https://github.com/llvm/llvm-project/commit/6102310d814ad73eab60a88b21dd70874f7a056f#diff-0f9a49c4e31c311a0010e126cd785f08 changed PHI node equality check, but there were some users that implicitly depended on the old definition of the PHI equality, and didn't verify their implicit assumptions with reality,
[LLVMdev] Building clang + libc++ + libc++abi
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
[LLVMdev] Linking Debug+Asserts Shared Library libclang.so: final link failed: Bad value
2013 May 22
2
[LLVMdev] Linking Debug+Asserts Shared Library libclang.so: final link failed: Bad value
...CFLAGS=-fPIC Now i get this strange error,cannot link, pls help...how to proceed. llvm[4]: Linking Debug+Asserts Shared Library libclang.so /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse-linux/bin/ld: /home1/ragha/llvmsrc/llvm-3.2.src/build/tools/clang/tools/libclang/Debug+Asserts/ARCMigrate.o: relocation R_X86_64_PC32 against `std::basic_string<char, std::char_traits<char>, std::allocator<char> >::data() const@@GLIBCXX_3.4' can not be used when making a shared object; recompile with -fPIC /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse-linux/bin/ld...
[LLVMdev] Targeting ARM Cortex-a9 from x86_64 with clang
2013 Nov 27
2
[LLVMdev] Targeting ARM Cortex-a9 from x86_64 with clang
On 26 Nov 2013, at 19:10, Joerg Sonnenberger <joerg at britannica.bec.de> wrote: > On Tue, Nov 26, 2013 at 12:40:17PM -0500, Sean Silva wrote: >> Well, just remember that the GNU binutils that those tools are derived from >> support far more architectures (3x, 5x?) than LLVM does (just supporting >> linux requires like 30 architectures). When we get to that point, it
[LLVMdev] [cfe-dev] Building clang + libc++ + libc++abi
2015 Jul 08
2
[LLVMdev] [cfe-dev] Building clang + libc++ + libc++abi
...-virtual -fno-strict-aliasing > -Wno-nested-anon-types -O3 -Wl,-O3 -Wl,--gc-sections > -Wl,--version-script,/ptmp/dag/build/clang/tools/clang/tools/libclang/libclang.exports > -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 >...
Disk space and RAM requirements in docs
2019 Apr 30
6
Disk space and RAM requirements in docs
...b/Analysis/CMakeFiles/LLVMAnalysis.dir 342M build/lib/Analysis/CMakeFiles 342M build/lib/Analysis 327M build/tools/lld 322M build/lib/Target/Mips 313M build/lib/Target/ARM/CMakeFiles/LLVMARMCodeGen.dir 313M build/lib/Target/ARM/CMakeFiles 307M build/lib/Target/WebAssembly 306M build/tools/clang/lib/ARCMigrate/CMakeFiles/clangARCMigrate.dir 306M build/tools/clang/lib/ARCMigrate/CMakeFiles 306M build/tools/clang/lib/ARCMigrate 304M build/lib/Target/AArch64/CMakeFiles/LLVMAArch64CodeGen.dir 304M build/lib/Target/AArch64/CMakeFiles 291M build/tools/polly 290M build/tools/polly/lib 285M build/lib/Target/Mips...