similar to: Function name demangle on clang vs clang++

Hi Osman, You can’t enable the static CRT through the command-line. You would need to apply this patch: https://reviews.llvm.org/D55056 (although it doesn’t work with lldb) Alex. ________________________________ De : llvm-dev <llvm-dev-bounces at lists.llvm.org> de la part de Osman Zakir via llvm-dev <llvm-dev at lists.llvm.org> Envoyé : 28 octobre 2019 07:47:43 À : llvm-dev at

I would really like to know about how to apply the patch for making MSVC-built LLVM executables lighter. But aside from that, I also want to know what LLVM does to CMake's default setting of /EHsc. I want to keep that setting on, but I can't figure out how. Any help is appreciated. Thanks in advance. P.S. The CMAKE_CXX_FLAGS variable isn't helping at all, otherwise I wouldn't

When I compile some code with the near-trunk clang++ I get this: ... tail call void @_Unwind_Resume_or_Rethrow(i8* %exn2) noreturn unreachable ... declare void @_Unwind_Resume_or_Rethrow(i8*) ... Same with __cxa_throw. 'noreturn' is missing on declarations. This seems to be a bug. Also can _Unwind_Resume_or_Rethrow actually return? When I run some simple exception code in JIT I

On Jul 15, 2010, at 3:31 PM, Yuri wrote: > When I compile some code with the near-trunk clang++ I get this: Please send clang-specific questions to cfe-dev at cs.uiuc.edu. > ... > tail call void @_Unwind_Resume_or_Rethrow(i8* %exn2) noreturn > unreachable > ... > declare void @_Unwind_Resume_or_Rethrow(i8*) > ... > > Same with __cxa_throw. 'noreturn' is

On Jul 15, 2010, at 5:51 PM, John McCall wrote: >> Also can _Unwind_Resume_or_Rethrow actually return? When I run some >> simple exception code in JIT I see that this function actually returns >> and then SEGVs. > > I have no idea what system you're on, but _Unwind_Resume_or_Rethrow really > isn't allowed to return. > It's not. But if the unwind

On 07/15/2010 18:30, Bill Wendling wrote: > It's not. But if the unwind library can't handle something, then the _Unwind_Resume_or_Rethrow could fall out of the function (it would assert in debug mode). Darwin's implementation of _URoR in libunwind does this. > > Isn't unwind library supposed to call terminate() every time it can't handle something? Yuri

On Jul 15, 2010, at 6:52 PM, Yuri wrote: > On 07/15/2010 18:30, Bill Wendling wrote: >> It's not. But if the unwind library can't handle something, then the _Unwind_Resume_or_Rethrow could fall out of the function (it would assert in debug mode). Darwin's implementation of _URoR in libunwind does this. >> > Isn't unwind library supposed to call terminate() every

Here http://llvm.org/docs/ExceptionHandling.html#llvm_eh_selector llvm.eh.selector is declared like this: i32 %llvm.eh.selector <http://llvm.org/docs/ExceptionHandling.html#llvm_eh_selector>(i8*, i8*, i8*, ...) But when clang++ (rev.121360) writes the module with exceptions, it writes it out like this: declare i32 @llvm.eh.selector(i8*, i8*, ...) nounwind Why there is such descrepancy?

di.cpp: ------ #include <iostream> using namespace std; struct foo { int a; int b; }; int main(int, char **) { const foo f = { .a = 10, .b = 11 }; cout << f.a << ' ' << f.b << endl; return 0; } ----- $ clang++ -Wall -Wextra -Weffc++ -o di di.cpp $ ./di 10 11 It is a standard C99! Or am I wrong? $ clang++ --version clang version 2.8

On Jan 13, 2011, at 1:33 PM, Andrey Valyaev wrote: > di.cpp: > ------ > #include <iostream> > using namespace std; > > struct foo { > int a; > int b; > }; > > int main(int, char **) > { > const foo f = { .a = 10, .b = 11 }; > cout << f.a << ' ' << f.b << endl; > return 0; > } > ----- > > $

I have C++ project that builds fine with g++. But when I try to replace g++ with clang++ I get such errors (see below) during link. What might be a problem? Yuri --- errors are like this --- local symbol 1: discarded in section `.text.SomeSymbolHere1' local symbol 2: discarded in section `.text.SomeSymbolHere2' ... ...

Hello Yuri, Did you look at http://cfe.llvm.org/compatibility.html yet? --Sam ----- Original Message ----- > From: Yuri <yuri at rawbw.com> > To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > Cc: > Sent: Saturday, June 11, 2011 12:22 PM > Subject: [LLVMdev] Build of C++ project with clang++ fails (local symbol 1: discarded in section `xxx') > >

Sean, It is llvm issue rather than clang. please subscribe llvmdev, too. 2011/11/19 Sean McBeth <daedalic at gmail.com>: > This seems like it should be simple, but I've run into quite a few problems > with this. I first tried using cout from <iostream.h>, only to find out that > llvm does not seem to support it. Then I tried using raw_ostream and the > outs function,

I did log it as a bug but thought I'd mention it here: http://llvm.org/bugs/show_bug.cgi?id=12862 This is from the ITK project (www.itk.org) -- well, actually the version of GDCM2 incorporated into ITK. I do regular builds using the SVN Trunk version of CLang of our largish C++ software suite for image processing, which includes building several prerequisite libraries. Today I updated

On Mon, May 28, 2012 at 07:42:12PM +0200, Mikael Lyngvig wrote: > Does Clang/Clang++ not have its own set of standard headers? Isn't this a > serious issue if Clang/Clang++ is ever to outdo GCC/G++? Is there any work > in progress on this? It provides the compiler-centric headers. It doesn't replace the rest of the C runtime library. That wouldn't make much sense. Joerg

Hi, I'm using LNT to run the llvm nightly tests. When it's compiling the tests, it seems to always use the clang++ driver as the linker command instead of clang, even for tests that are pure C code. This makes all the binaries depend on libstdc++, which isn't great. This happens even if I specify --disable-cxx. The only way around it seems to be to also specify clang as the C++

Hi, I`m working with processor models. I´m using clang++ to preprocess and compile my application stopping it (-S) before the assembler because I would like to use a different assembler (it comes from another processor model). It seems that the output assembly code is not compatible with the assembler but I´M not sure about that. The errors are with @progbits, weak and hidden sections. See below:

Hello It looks like Ubuntu 13.04 has changed the include files directories structure Now we get the following error in many of our programs that compile fine on Ubuntu 12.04 > clang++ -c -x c++ -emit-llvm > ../../libsimsoc/processors/ppc/ppc_llvm_lib.cpp -DNDEBUG > -I/home/vania/systemc-2.3.0/include -I/home/vania/tlm2.0/include/tlm > -DSC_INCLUDE_DYNAMIC_PROCESSES

Hi, it looks like you're compiling CUDA for an ARM host? This is not a configuration we have tested, nor is it something we have the capability of testing at the moment. You may be able to make it work by providing the appropriate -isystem flags to clang so that it can find your headers, but who knows, it may be more complicated than that. Regards, -Justin On Wed, Oct 26, 2016 at 9:59 PM,

(+llvm-dev) My question was whether your host machine, the one which is running the compiler, is ARM (as opposed to x86 or POWER). The header you pointed to was in "aarch64-linux-gnu", which made me think you might be on an ARM system. If you are not running linux x86, it is not likely to work. If you are running linux x86, we will need much more details about your system in order to