commit | 260b4151c830b74c3dfa686aa982a3a592ddfb0b | [log] [tgz] |
---|---|---|
author | Rasmus Brandt <brandtr@webrtc.org> | Thu Aug 30 15:24:27 2018 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Aug 30 15:24:47 2018 |
tree | a66d068055de0c93173a67bc2358e5e3ac5358c4 | |
parent | 7bcd2a98be3fa8c246866d6b343c7f94752977b3 [diff] |
Revert "Reland "Optimize execution time of RTPSender::UpdateDelayStatistics"" This reverts commit 7bcd2a98be3fa8c246866d6b343c7f94752977b3. Reason for revert: peerconnection_unittests fails on downstream test runner. Original change's description: > Reland "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: I493de337bf20c998aa32c2532212cac85c5517fb > Reviewed-on: https://webrtc-review.googlesource.com/96641 > Reviewed-by: Philip Eliasson <philipel@webrtc.org> > Reviewed-by: Åsa Persson <asapersson@webrtc.org> > Commit-Queue: Björn Terelius <terelius@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#24501} TBR=terelius@webrtc.org,asapersson@webrtc.org,philipel@webrtc.org Change-Id: Ia48444d2a7647cf826ef93b4720f6d7ff9a712c3 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:9439 Reviewed-on: https://webrtc-review.googlesource.com/96960 Reviewed-by: Rasmus Brandt <brandtr@webrtc.org> Commit-Queue: Rasmus Brandt <brandtr@webrtc.org> Cr-Commit-Position: refs/heads/master@{#24502}
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.