maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/compiler-rt/lib/profile/InstrProfilingPlatformDarwin.c

44 lines
1.8 KiB
C
Raw Normal View History

InstrProf: Reorganize files; no functionality change Move functions around to prepare for some other changes. - Merge InstrProfilingExtras.h with InstrProfiling.h. There's no benefit to having these split. - Rename InstrProfilingExtras.c to InstrProfilingFile.c. - Split actual buffer writing code out of InstrProfiling.c into InstrProfilingBuffer.c. - Drive-by corrections of a couple of header comments. <rdar://problem/15943240> llvm-svn: 204497
2014-03-22 02:29:15 +08:00
/*===- InstrProfilingPlatformDarwin.c - Profile data on Darwin ------------===*\
PGO: Implement Darwin linker magic for instrumentation Use Darwin linker magic to find bounds of instrumentation data sections at link time instead of runtime. <rdar://problem/15943240> llvm-svn: 204302
2014-03-20 11:57:33 +08:00
|*
|* The LLVM Compiler Infrastructure
|*
|* This file is distributed under the University of Illinois Open Source
|* License. See LICENSE.TXT for details.
|*
\*===----------------------------------------------------------------------===*/
#include "InstrProfiling.h"
[profile] Flatten profile runtime - define platform-specific code in sources, not in the build system llvm-svn: 206915
2014-04-23 02:49:32 +08:00
#if defined(__APPLE__)
PGO: Implement Darwin linker magic for instrumentation Use Darwin linker magic to find bounds of instrumentation data sections at link time instead of runtime. <rdar://problem/15943240> llvm-svn: 204302
2014-03-20 11:57:33 +08:00
/* Use linker magic to find the bounds of the Data section. */
InstrProf: Fix shared object profiling Change the API of the instrumented profiling library to work with shared objects. - Most things are now declared hidden, so that each executable gets its own copy. - Initialization hooks up a linked list of writers. - The raw format with shared objects that are profiled consists of a concatenated series of profiles. llvm-profdata knows how to deal with that since r208938. <rdar://problem/16918688> llvm-svn: 208940
2014-05-16 09:30:24 +08:00
__attribute__((visibility("hidden")))
PGO: Change runtime prefix from pgo to profile These functions are in the profile runtime. PGO comes later. Unfortunately, there's only room for 16 characters in a Darwin section, so use __llvm_prf_ instead of __llvm_profile_ for section names. <rdar://problem/15943240> llvm-svn: 204391
2014-03-21 04:00:44 +08:00
extern __llvm_profile_data DataStart __asm("section$start$__DATA$__llvm_prf_data");
InstrProf: Fix shared object profiling Change the API of the instrumented profiling library to work with shared objects. - Most things are now declared hidden, so that each executable gets its own copy. - Initialization hooks up a linked list of writers. - The raw format with shared objects that are profiled consists of a concatenated series of profiles. llvm-profdata knows how to deal with that since r208938. <rdar://problem/16918688> llvm-svn: 208940
2014-05-16 09:30:24 +08:00
__attribute__((visibility("hidden")))
PGO: Change runtime prefix from pgo to profile These functions are in the profile runtime. PGO comes later. Unfortunately, there's only room for 16 characters in a Darwin section, so use __llvm_prf_ instead of __llvm_profile_ for section names. <rdar://problem/15943240> llvm-svn: 204391
2014-03-21 04:00:44 +08:00
extern __llvm_profile_data DataEnd __asm("section$end$__DATA$__llvm_prf_data");
InstrProf: Fix shared object profiling Change the API of the instrumented profiling library to work with shared objects. - Most things are now declared hidden, so that each executable gets its own copy. - Initialization hooks up a linked list of writers. - The raw format with shared objects that are profiled consists of a concatenated series of profiles. llvm-profdata knows how to deal with that since r208938. <rdar://problem/16918688> llvm-svn: 208940
2014-05-16 09:30:24 +08:00
__attribute__((visibility("hidden")))
PGO: Change runtime prefix from pgo to profile These functions are in the profile runtime. PGO comes later. Unfortunately, there's only room for 16 characters in a Darwin section, so use __llvm_prf_ instead of __llvm_profile_ for section names. <rdar://problem/15943240> llvm-svn: 204391
2014-03-21 04:00:44 +08:00
extern char NamesStart __asm("section$start$__DATA$__llvm_prf_names");
InstrProf: Fix shared object profiling Change the API of the instrumented profiling library to work with shared objects. - Most things are now declared hidden, so that each executable gets its own copy. - Initialization hooks up a linked list of writers. - The raw format with shared objects that are profiled consists of a concatenated series of profiles. llvm-profdata knows how to deal with that since r208938. <rdar://problem/16918688> llvm-svn: 208940
2014-05-16 09:30:24 +08:00
__attribute__((visibility("hidden")))
PGO: Change runtime prefix from pgo to profile These functions are in the profile runtime. PGO comes later. Unfortunately, there's only room for 16 characters in a Darwin section, so use __llvm_prf_ instead of __llvm_profile_ for section names. <rdar://problem/15943240> llvm-svn: 204391
2014-03-21 04:00:44 +08:00
extern char NamesEnd __asm("section$end$__DATA$__llvm_prf_names");
InstrProf: Fix shared object profiling Change the API of the instrumented profiling library to work with shared objects. - Most things are now declared hidden, so that each executable gets its own copy. - Initialization hooks up a linked list of writers. - The raw format with shared objects that are profiled consists of a concatenated series of profiles. llvm-profdata knows how to deal with that since r208938. <rdar://problem/16918688> llvm-svn: 208940
2014-05-16 09:30:24 +08:00
__attribute__((visibility("hidden")))
PGO: Change runtime prefix from pgo to profile These functions are in the profile runtime. PGO comes later. Unfortunately, there's only room for 16 characters in a Darwin section, so use __llvm_prf_ instead of __llvm_profile_ for section names. <rdar://problem/15943240> llvm-svn: 204391
2014-03-21 04:00:44 +08:00
extern uint64_t CountersStart __asm("section$start$__DATA$__llvm_prf_cnts");
InstrProf: Fix shared object profiling Change the API of the instrumented profiling library to work with shared objects. - Most things are now declared hidden, so that each executable gets its own copy. - Initialization hooks up a linked list of writers. - The raw format with shared objects that are profiled consists of a concatenated series of profiles. llvm-profdata knows how to deal with that since r208938. <rdar://problem/16918688> llvm-svn: 208940
2014-05-16 09:30:24 +08:00
__attribute__((visibility("hidden")))
PGO: Change runtime prefix from pgo to profile These functions are in the profile runtime. PGO comes later. Unfortunately, there's only room for 16 characters in a Darwin section, so use __llvm_prf_ instead of __llvm_profile_ for section names. <rdar://problem/15943240> llvm-svn: 204391
2014-03-21 04:00:44 +08:00
extern uint64_t CountersEnd __asm("section$end$__DATA$__llvm_prf_cnts");
PGO: Implement Darwin linker magic for instrumentation Use Darwin linker magic to find bounds of instrumentation data sections at link time instead of runtime. <rdar://problem/15943240> llvm-svn: 204302
2014-03-20 11:57:33 +08:00
InstrProf: Fix shared object profiling Change the API of the instrumented profiling library to work with shared objects. - Most things are now declared hidden, so that each executable gets its own copy. - Initialization hooks up a linked list of writers. - The raw format with shared objects that are profiled consists of a concatenated series of profiles. llvm-profdata knows how to deal with that since r208938. <rdar://problem/16918688> llvm-svn: 208940
2014-05-16 09:30:24 +08:00
__attribute__((visibility("hidden")))
profile: Avoid name collisions between instrumentation and runtime The naming scheme we're using for counters in profile data shares a prefix with some fixed names we use for the runtime, notably __llvm_profile_data_begin and _end. Embarrassingly, this means a function called begin() can't be instrumented. This modifies the runtime names so as not to collide with the instrumentation. llvm-svn: 217166
2014-09-04 23:45:31 +08:00
const __llvm_profile_data *__llvm_profile_begin_data(void) {
PGO: Declare zero-argument C functions as foo(void) It turns out this is C code. Specify foo(void). <rdar://problem/15943240> llvm-svn: 204396
2014-03-21 04:55:00 +08:00
return &DataStart;
}
InstrProf: Fix shared object profiling Change the API of the instrumented profiling library to work with shared objects. - Most things are now declared hidden, so that each executable gets its own copy. - Initialization hooks up a linked list of writers. - The raw format with shared objects that are profiled consists of a concatenated series of profiles. llvm-profdata knows how to deal with that since r208938. <rdar://problem/16918688> llvm-svn: 208940
2014-05-16 09:30:24 +08:00
__attribute__((visibility("hidden")))
profile: Avoid name collisions between instrumentation and runtime The naming scheme we're using for counters in profile data shares a prefix with some fixed names we use for the runtime, notably __llvm_profile_data_begin and _end. Embarrassingly, this means a function called begin() can't be instrumented. This modifies the runtime names so as not to collide with the instrumentation. llvm-svn: 217166
2014-09-04 23:45:31 +08:00
const __llvm_profile_data *__llvm_profile_end_data(void) {
PGO: Declare zero-argument C functions as foo(void) It turns out this is C code. Specify foo(void). <rdar://problem/15943240> llvm-svn: 204396
2014-03-21 04:55:00 +08:00
return &DataEnd;
}
InstrProf: Fix shared object profiling Change the API of the instrumented profiling library to work with shared objects. - Most things are now declared hidden, so that each executable gets its own copy. - Initialization hooks up a linked list of writers. - The raw format with shared objects that are profiled consists of a concatenated series of profiles. llvm-profdata knows how to deal with that since r208938. <rdar://problem/16918688> llvm-svn: 208940
2014-05-16 09:30:24 +08:00
__attribute__((visibility("hidden")))
profile: Avoid name collisions between instrumentation and runtime The naming scheme we're using for counters in profile data shares a prefix with some fixed names we use for the runtime, notably __llvm_profile_data_begin and _end. Embarrassingly, this means a function called begin() can't be instrumented. This modifies the runtime names so as not to collide with the instrumentation. llvm-svn: 217166
2014-09-04 23:45:31 +08:00
const char *__llvm_profile_begin_names(void) { return &NamesStart; }
InstrProf: Fix shared object profiling Change the API of the instrumented profiling library to work with shared objects. - Most things are now declared hidden, so that each executable gets its own copy. - Initialization hooks up a linked list of writers. - The raw format with shared objects that are profiled consists of a concatenated series of profiles. llvm-profdata knows how to deal with that since r208938. <rdar://problem/16918688> llvm-svn: 208940
2014-05-16 09:30:24 +08:00
__attribute__((visibility("hidden")))
profile: Avoid name collisions between instrumentation and runtime The naming scheme we're using for counters in profile data shares a prefix with some fixed names we use for the runtime, notably __llvm_profile_data_begin and _end. Embarrassingly, this means a function called begin() can't be instrumented. This modifies the runtime names so as not to collide with the instrumentation. llvm-svn: 217166
2014-09-04 23:45:31 +08:00
const char *__llvm_profile_end_names(void) { return &NamesEnd; }
InstrProf: Fix shared object profiling Change the API of the instrumented profiling library to work with shared objects. - Most things are now declared hidden, so that each executable gets its own copy. - Initialization hooks up a linked list of writers. - The raw format with shared objects that are profiled consists of a concatenated series of profiles. llvm-profdata knows how to deal with that since r208938. <rdar://problem/16918688> llvm-svn: 208940
2014-05-16 09:30:24 +08:00
__attribute__((visibility("hidden")))
profile: Avoid name collisions between instrumentation and runtime The naming scheme we're using for counters in profile data shares a prefix with some fixed names we use for the runtime, notably __llvm_profile_data_begin and _end. Embarrassingly, this means a function called begin() can't be instrumented. This modifies the runtime names so as not to collide with the instrumentation. llvm-svn: 217166
2014-09-04 23:45:31 +08:00
uint64_t *__llvm_profile_begin_counters(void) { return &CountersStart; }
InstrProf: Fix shared object profiling Change the API of the instrumented profiling library to work with shared objects. - Most things are now declared hidden, so that each executable gets its own copy. - Initialization hooks up a linked list of writers. - The raw format with shared objects that are profiled consists of a concatenated series of profiles. llvm-profdata knows how to deal with that since r208938. <rdar://problem/16918688> llvm-svn: 208940
2014-05-16 09:30:24 +08:00
__attribute__((visibility("hidden")))
profile: Avoid name collisions between instrumentation and runtime The naming scheme we're using for counters in profile data shares a prefix with some fixed names we use for the runtime, notably __llvm_profile_data_begin and _end. Embarrassingly, this means a function called begin() can't be instrumented. This modifies the runtime names so as not to collide with the instrumentation. llvm-svn: 217166
2014-09-04 23:45:31 +08:00
uint64_t *__llvm_profile_end_counters(void) { return &CountersEnd; }
[profile] Flatten profile runtime - define platform-specific code in sources, not in the build system llvm-svn: 206915
2014-04-23 02:49:32 +08:00
#endif