summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSung Yoon Whang <suwhang@microsoft.com>2018-05-10 19:57:47 -0700
committerNoah Falk <noahfalk@users.noreply.github.com>2018-05-10 19:57:47 -0700
commite5299e87b6eda43acb12a3cb341b71e8a3121960 (patch)
tree3c0503bf57c9754713f11d130d19f29158c33333
parent02cec57013da10f08fb73f554460ed4fd962ae0e (diff)
downloadcoreclr-e5299e87b6eda43acb12a3cb341b71e8a3121960.tar.gz
coreclr-e5299e87b6eda43acb12a3cb341b71e8a3121960.tar.bz2
coreclr-e5299e87b6eda43acb12a3cb341b71e8a3121960.zip
update profiler API status to reflect that #13153 is resolved (#17953)
-rw-r--r--Documentation/project-docs/profiling-api-status.md4
1 files changed, 0 insertions, 4 deletions
diff --git a/Documentation/project-docs/profiling-api-status.md b/Documentation/project-docs/profiling-api-status.md
index 599e8c1897..1cd9c7eb55 100644
--- a/Documentation/project-docs/profiling-api-status.md
+++ b/Documentation/project-docs/profiling-api-status.md
@@ -14,10 +14,6 @@ The .NET Core project started with the codebase from the desktop CoreCLR/Silverl
The implementation of this API was making some questionable assumptions about Windows OS API behavior in order to walk callstacks asynchronously. When operating in this async mode we aren't yet confident we can produce reasonable implementations for other platforms. Our understanding is that most users of this API are attempting to do sample based profiling. If so we think it may be easier to offer a runtime provided event stream of sample callstacks to accomplish the same scenario without needing the API, but we also haven't heard any demand for it. Feedback welcome!
-### Profiler does not disable Concurrent GC
-
-See github issue [#13153](https://github.com/dotnet/coreclr/issues/13153) for more details.
-
### ReJIT on ARM
ReJIT feature is only available on x86/x64 for now.