Commit Graph

7 Commits

Author SHA1 Message Date
Mike Ash
f48bd293cb [Runtime] Remove RuntimeFunctionCounters in no-assert builds.
A build option to include or exclude RuntimeFunctionCounters. By default, it's enabled when assertions are enabled.

rdar://problem/35864525
2018-01-25 12:18:25 -05:00
Roman Levenstein
68d7778add Address post-commit review comments on PR #11910
- Use SWIFT_RUNTIME_EXPORT instead of SWIFT_RT_ENTRY_VISIBILITY for exposed functions
- Use `_swift_`  prefixes on the names of exposed functions
- Make the global counters and per-object counters cache thread-safe by using locks
2017-10-24 15:49:37 -07:00
Roman Levenstein
acff3212b5 Add a comment explaining why the file needs to be compiled even in no-asserts builds 2017-09-18 13:18:27 -07:00
Roman Levenstein
51bb830763 #include should be on the next line after #define 2017-09-18 13:17:48 -07:00
Roman Levenstein
d8c5238449 Move FUNCTION_TO_TRACK definitions closer to the includes of "RuntimeInvocationsTracking.def" 2017-09-18 12:52:40 -07:00
Roman Levenstein
1996d5fb64 Address review comments. 2017-09-15 16:39:08 -07:00
Roman Levenstein
ec1e051a36 Add runtime library support for tracking the invocations of runtime functions. 2017-09-14 16:43:13 -07:00