search for: femit

...ng simple test case- #include <iostream> int func(int* ptr){ std::cout << *ptr; return *ptr + 5; } int main(int argc, char** argv){ int a = 4; int* ptr_a = &a; int b = func(ptr_a); return 0; } commandline used -- bash$ clang++ -Xclang -femit-debug-entry-values -O2 -ggdb test.cpp For this case-- these Tags are not emitted DW_TAG_call_site, DW_TAG_call_site_paramter .. only DW_AT_GNU_all_call_sites attribute is present. + @Djorde DW_TAG_call_site are supported using late MIR approach, are the new Call Site related development will be s...

...also the IR-level flag (DIFlagAllCallsDescribed) that lowers to > the DW_AT_call_all_calls. > > There is also support for call-site-parameter (DW_TAG_call_site_parameter) and the debug entry values > (DW_OP_entry_value) related DWARF 5 symbols, but it is restricted by the CC1 option ‘-femit-debug-entry-values’, > since the LLDB is still missing support for that. Not for too long ;) See https://reviews.llvm.org/D67410 <https://reviews.llvm.org/D67410> & https://reviews.llvm.org/D67376 <https://reviews.llvm.org/D67376> best, vedant > > Best regards, > Dj...

Hello, We have a user that wants to get the code coverage report for his library without turning on instrumentation for the library clients or change how they are built (only the library is instrumented). It seems like the inline member functions defined in headers are not instrumented in this case because the clients are not instrumented. The library itself does not have a copy of the inline

Hello All, I was working on some dwarf-5 features and debugging optimized code support in clang and llvm. Noticed that, DW_TAG_call_site is supported in llvm middle-end. but clang is not emitting these. I was hoping, if someone could provide current status of these features and current status of dwarf-5 features in clang and llvm. That will be immensely helpful. Thanks! Sourabh. --------------

Seems like -femit-all-decls partially works around this. But I would still like to solve the real problem of creating a function which is local/static but which cannot be thrown away by the optimizer if not referenced. On 07/24/2013 04:07 PM, Reed Kotler wrote: > Maybe there is some attribute I can add this...

...shared libraries. It¹s a simple fix, just adding a few COMPILER_RT_VISIBILITY (i.e. __attribute__((visibility("hidden")))) in GCDAProfiling.c. Now, I¹d like to include a test program to demonstrate the fix. AFAICT, there seems to be a single test for "-fprofile­arcs/-ftest-coverage/-femit-coverage-data", namely: tools/clang/test/CodeGen/code-coverage.c. (To be fair, there are some tests related to the testing of the command line options themselves.) There seems to be no tests that actually execute the instrumented executables to gather coverage data. - Is that a fair assessmen...

Hello, I am working on the assembly printer for RISC-V, more specifically on the AsmPrinter class. I altered the RISCV Backend to print C code instead of Assembly, interpreted by libraries... (but that's not important) My problem is that, for my application to work, I need to treat my functions in the order they are in the original C file. I discovered that these functions are not treated

Ah ok. Sorry. :) I think that argument "-femit-all-decls" will help you. Olivier. On Mon, Dec 14, 2009 at 9:18 PM, Arvind Sudarsanam < arvind.sudarsanam at aggiemail.usu.edu> wrote: > Hi, > > Sorry for not being specific. I just wanted to know if there is any > way at all to force clang to generate intermediate code fo...

In many cases, the line-table fussing to improve autoFDO/sample-PGO would also likely help the debugging experience for optimized code, certainly in cases where line attribution is inherently ambiguous. In those cases, I have no problem with Just Doing It. Something likely to pad the line table to benefit profiling without similarly benefiting debugging… that's probably worth inventing a

Hi, Sorry for not being specific. I just wanted to know if there is any way at all to force clang to generate intermediate code for static functions when they are not being called anywhere inside the current module. Other compilers seem to generate intermediate code (lcc, for instance). Thanks for your reply..Olivier. Sincerely Arvind On Mon, Dec 14, 2009 at 1:10 PM, Olivier Meurant

...ull # -mmacosx-version-min=10.5.6 -mtune=generic -march=nocona -auxbase # -fverbose-asm -D__private_extern__=extern # options enabled: -fPIC -falign-jumps-max-skip -falign-loops # -falign-loops-max-skip -fargument-alias -fbranch-count-reg -fcommon # -fearly-inlining -feliminate-unused-debug-types -femit-class-debug-always # -fexceptions -ffunction-cse -fgcse-lm -fglobal-alloc-prefer-bytes -fident # -finline-functions-called-once -fivopts -fkeep-static-consts # -fleading-underscore -flocal-alloc -fmove-loop-invariants -fpeephole # -freg-struct-return -fsched-interblock -fsched-spec # -fsched-stalle...

Maybe there is some attribute I can add this will not allow the function to be discarded. On 07/24/2013 03:45 PM, reed kotler wrote: > I have some stub functions that are essentially static, but they cannot > be removed. > > What linkage type should I use in that case. Internal linkage appears to > get the functions discarded if they are not referenced under certain >

On Mon, Jan 4, 2010 at 5:41 AM, Kenneth Uildriks <kennethuil at gmail.com>wrote: > On Mon, Jan 4, 2010 at 4:43 AM, Russell Wallace > <russell.wallace at gmail.com> wrote: > > When implementing a language using LLVM as the backend, it is > > necessary to give programs written in that language, access to the C > > standard library functions. The Kaleidoscope

I have some stub functions that are essentially static, but they cannot be removed. What linkage type should I use in that case. Internal linkage appears to get the functions discarded if they are not referenced under certain optimizations. This is part of the gcc mips16 hack for floating point. For example, a function like floor from the math library will be called with an external

...; [ 1] GCC: (GNU) 4.9.x-google 20150123 (prerelease) > > Is there any similar flags we should use? > If it's the sort of issue I'm guessing it might be (though I have very little evidence to go on/I don't remember the possible/specific failure modes, etc) you might try -femit-class-debug-always with GCC That said, to provide a more accurate diagnosis/help, a reduced test case would be really helpful (the smallest C++ input (counting headers, etc, as well - tools like creduce/delta/multidelta can help reduce test cases, though they're better on compiler crashes than...

Thanks David. I meant to send to lldb maillist, but glad to hear response here. Our binary is built from gcc: String dump of section '.comment': [ 1] GCC: (GNU) 4.9.x-google 20150123 (prerelease) Is there any similar flags we should use? By doing "strings -a [binary] | grep -i gcc", I found the following flags being used: GNU C++ 4.9.x-google 20150123 (prerelease)

Hi all, Many of us find ourselves spending a great chunk of time comparing LLVM IR dumps at various stages of compilation pipeline or after a given optimization pass. Said process can be extremely laborious, and this is especially true when comparing shaders or compute modules. Important semantic differences are often difficult to spot because of the irregular naming and ordering of instructions.

If you're going to use clang built binaries with lldb, you'll want to pass -fstandalone-debug - this is the default on platforms where lldb is the primary debugger (Darwin and freebsd) Not sure if that is the problem you are seeing, but will be a problem sooner or later On Mar 26, 2016 4:16 PM, "Jeffrey Tan via llvm-dev" <llvm-dev at lists.llvm.org> wrote: > Hi, >