similar to: failure at link time 3.9.1

I was able to add a call to EmitFunctionDecl in lib/CodeGen/CodeGenModule.cpp and then needed a corresponding LLVM change to handle Subprogram¹s in the retained type vector. The diff D18565 is marked Abandoned. What is the future plans for supporting full-type consumers? On 12/9/16, 2:24 PM, "aprantl at apple.com on behalf of Adrian Prantl" <aprantl at apple.com> wrote: >

Hello, since r243376 clang does not build with new libc++ anymore. Log attached. Reverting back lib/libc++ or not using libc++ fixes it. System: stable/9 amd64 r243742 WITHOUT_LIB32=yes WITHOUT_PROFILE=yes WITHOUT_SYSINSTALL=yes WITH_CLANG=yes WITH_CLANG_EXTRAS=yes WITH_CLANG_IS_CC=yes WITH_LIBCPLUSPLUS=yes CPUTYPE?=athlon64-sse3 CXXFLAGS+= -stdlib=libc++ -std=c++11 CC=clang CPP=clang-cpp

Hi, I'm having a hard time linking the LLVM/clang libraries in Xcode. I've been fighting this for a couple of days now, and decided to make a fresh checkout and a super-simple demo project to try and isolate the problem, but even so I'm getting undefined symbol errors in the linker for the static libraries LLVM is producing. This is really baffling, so probably I'm

> On Dec 9, 2016, at 2:16 PM, David Callahan <dcallahan at fb.com> wrote: > > Adrian, this appears to generate, in my example below, the return type for > the external function (“foo” below) but does not generate a (in Dwarf) > DW_TAG_Subprogram which binds that type to the name. Is that expected? > We are probably not visiting forward declarations in CGDebugInfo. You

We have a similar problem in Mesa's radeonsi driver. It would be great if command-line options could somehow be tied to an llvm::Context, for example. There is an even worse problem when *different versions* of LLVM are loaded into the same process. This is basically guaranteed to lead to crashes because of symbol clashes. I wonder if C++11 inline namespaces could be used for proper

Hi, On the OpenMandriva side, x86_64 passes all checks. We're having some problems with other architectures though (see below): x86_64 succeeded, packages are here: https://abf.openmandriva.org/build_lists/76792 i586 fails to build, but this seems to be an issue with 3.8.1 (which we're using to build 3.9): /usr/bin/clang++ -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS

On 07.05.2018 17:49, Tom Stellard wrote: > On 05/07/2018 12:28 AM, Nicolai Hähnle via llvm-dev wrote: >> We have a similar problem in Mesa's radeonsi driver. It would be great if command-line options could somehow be tied to an llvm::Context, for example. >> >> There is an even worse problem when *different versions* of LLVM are loaded into the same process. This is

Hello everyone, A while back I hit an issue where the presence of multiple OpenCL runtimes on a single system triggered errors in libLLVM caused by redeclaring command line arguments [0]. There's been some discussion on the bug report and a pointer to a slightly older report, unrelated to OpenCL, but most likely about the same issue [1]. OpenCL uses an ICD loader library to abstract away

On 05/07/2018 12:28 AM, Nicolai Hähnle via llvm-dev wrote: > We have a similar problem in Mesa's radeonsi driver. It would be great if command-line options could somehow be tied to an llvm::Context, for example. > > There is an even worse problem when *different versions* of LLVM are loaded into the same process. This is basically guaranteed to lead to crashes because of symbol

Since we are only a week away from branching for 3.7.0, this new breakage in the stage2 bootstrap of llvm/clang/compiler-rt/clang-tools-extra should get triaged. At r241513, a three stage bootstrap with comparision of stage2/stage3 files completed fine. However at r241594 we now have the new regression reported in https://llvm.org/bugs/show_bug.cgi?id=24054... Assertion failed: (Val &&

On Feb 28, 2011, at 8:07 PM, Félix Cloutier wrote: > I'm using Xcode 3 to program with LLVM and Clang (both about yesterday's latest revisions), and when I compile, I get 1501 link-time warnings. All those I read were about symbol visibility. Here's an example: > > ld: warning: namespace::class::method() has different visibility (default) in

A change between r231216 and r231221 causes an assertion failure on the LLDB FreeBSD bot. The compiler is FreeBSD's in-tree one: FreeBSD clang version 3.5.1 (tags/RELEASE_351/final 225668) 20150115 First failing build: http://lab.llvm.org:8011/builders/lldb-x86_64-freebsd/builds/4668/steps/compile/logs/stdio Assertion: Assertion failed: ((!DD->isTrivial() ||

I'm using Xcode 3 to program with LLVM and Clang (both about yesterday's latest revisions), and when I compile, I get 1501 link-time warnings. All those I read were about symbol visibility. Here's an example: ld: warning: namespace::class::method() has different visibility (default) in /usr/local/lib/libclangCodeGen.a(CodeGenAction.o) and (hidden) in

I am interested in putting together a tool which can verify that an external declaration conforms with the actual definition. A.c: extern int32_t foo(); Int bar() { return foo(); } B.c: int64_t foo() { ... } I had thought that I could use the debug information but the debug information in A.o does not include the type of the declaration "foo", just the type of bar. Is there a way to

Hi, In another post I was trying to find out how to use libc++ instead of libstdc++ when compiling llvm/clang. I couldnt find the a way to tell cmake to do that. So I switched to using configure to compile llvm/clang. But now I find that the artifacts produced are different. Here are the issues I see: - configure doesnt seem to respect '--prefix' option, it just puts

2015-12-01 1:20 GMT+08:00 Chris Bieneman <beanz at apple.com>: > > On Nov 29, 2015, at 9:09 PM, 慕冬亮 <mudongliangabcd at gmail.com> wrote: > > 2015-11-30 12:58 GMT+08:00 Chris Bieneman <beanz at apple.com>: > > The autotools build system is officially deprecated and will be removed in a > future release. > > CMake is the recommended configuration system,

Hi, On a 1296-core Intel machine with 376 GB, setting -DLLVM_PARALLEL_LINK_JOB=1 does not help (switching back to ld scales) see: [5085/5201] Linking CXX executable bin/clang-11 FAILED: bin/clang-11 : && /home/usr4/c74014i/opt/clang/current/bin/clang++ -stdlib=libc++ -fPIC -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra

On Sun, Mar 22, 2020 at 9:05 PM Andrew Kelley <andrew at ziglang.org> wrote: > > On 3/19/20 9:51 AM, Hans Wennborg via llvm-dev wrote: > > Release Candidate 5 was just tagged as llvmorg-10.0.0-rc5 on the > > release branch at 35627038123. > > > > Source code and docs are available at > > https://prereleases.llvm.org/10.0.0/#rc5 and > >

On Tue, Dec 20, 2016 at 5:49 AM, Carsten Mattner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Hi again, Teresa. > > Looks like I had forgotten to report back with success > when finally building 3.9.0 in ThinLTO linker mode > back in October. Sorry about that and thanks for > helping me out. I know how important it is to get > success reports as well, as a

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