commit | 8b7bc5d7010c84ac57459518fe18309ef5fee1dd | [log] [tgz] |
---|---|---|
author | Johannes Kron <kron@webrtc.org> | Tue Sep 25 12:05:27 2018 +0000 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Sep 25 12:05:39 2018 +0000 |
tree | 3d1c362272d4f365e2fe5cf3ac8d8ee1f69b082c | |
parent | defb717811541a6a54f4d133ea3f27da9ed75752 [diff] |
Revert "Second reland of "Optimize execution time of RTPSender::UpdateDelayStatistics"" This reverts commit 9def3b45ef06de9e068e8f4d1644e9d508baa913. Reason for revert: webrtc_perf_tests fails on Mac-10.12. Original change's description: > Second reland of "Optimize execution time of RTPSender::UpdateDelayStatistics" > > The reland has a lot of additional DCHECKS for easier debugging, > so in debug builds it will actually be a ~2x slowdown compared to the old code. > The excessive DCHECKS should be removed in a followup CL. > > Bug: webrtc:9439 > Change-Id: I8389cd84f1ca12c29cc6993f0d2cf7e6d7dd8379 > Reviewed-on: https://webrtc-review.googlesource.com/101761 > Reviewed-by: Åsa Persson <asapersson@webrtc.org> > Reviewed-by: Björn Terelius <terelius@webrtc.org> > Commit-Queue: Johannes Kron <kron@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#24821} TBR=terelius@webrtc.org,asapersson@webrtc.org,kron@webrtc.org Change-Id: I98c4c96d552858d0299d49993e9b9be6a6204dfe No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:9439 Reviewed-on: https://webrtc-review.googlesource.com/101860 Reviewed-by: Johannes Kron <kron@webrtc.org> Commit-Queue: Johannes Kron <kron@webrtc.org> Cr-Commit-Position: refs/heads/master@{#24825}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.