search for: compiler_rt_visibility

Displaying 4 results from an estimated 4 matches for "compiler_rt_visibility".

2017 Dec 19
3
Question about : lprofValueProfNodes
...ned in compiler-rt: InstrProfilingValue.c but I can’t find where it is used? And the comment on it does not say much about why we need it either. Can someone explain why we need this and where it is used? /* A shared static pool in addition to the vnodes statically * allocated by the compiler. */ COMPILER_RT_VISIBILITY ValueProfNode lprofValueProfNodes[INSTR_PROF_VNODE_POOL_SIZE] COMPILER_RT_SECTION(COMPILER_RT_SEG INSTR_PROF_VNODES_SECT_NAME_STR); Thanks A -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20171219/ad63ed...
2017 Dec 20
2
Question about : lprofValueProfNodes
...ut why we need it either. It's used to avoid calling malloc(), which David (CC'd) found to be a performance improvement. best, vedant Can someone explain why we need this and where it is used? /* A shared static pool in addition to the vnodes statically * allocated by the compiler. */ COMPILER_RT_VISIBILITY ValueProfNode lprofValueProfNodes[INSTR_PROF_VNODE_POOL_SIZE] COMPILER_RT_SECTION(COMPILER_RT_SEG INSTR_PROF_VNODES_SECT_NAME_STR); Thanks A _______________________________________________ LLVM Developers mailing list llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org> http://...
2017 Dec 20
2
Question about : lprofValueProfNodes
...alling malloc(), which David (CC'd) found to be a > performance improvement. > > best, > vedant > > > Can someone explain why we need this and where it is used? > > /* A shared static pool in addition to the vnodes statically > * allocated by the compiler. */ > COMPILER_RT_VISIBILITY ValueProfNode > lprofValueProfNodes[INSTR_PROF_VNODE_POOL_SIZE] > COMPILER_RT_SECTION(COMPILER_RT_SEG INSTR_PROF_VNODES_SECT_NAME_STR); > > Thanks > A > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org >...
2016 Apr 06
2
Writing a test for gcov style coverage crashing after dlclose
Hi Everyone, I have uploaded a patch that allows one to successfully gather gcov/gcda coverage information on programs which unload 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....