Use explicit moves when returning covariant std::unique_ptr

In C++11 gcc and clang don't agree on whether the return
statement needs a std::move when returning a covariant
unique_ptr (i.e. the function signature expects a
unique_ptr<Base> and we try to return an instance of
unique_ptr<Derived>).
Fix the problem by making the cast+move explicit.
See discussion in https://android-review.googlesource.com/c/platform/external/perfetto/+/1127105

Bug: 141319349
Change-Id: Iffc4fc7f76f292614a22501a151837856a0cdb90
3 files changed
tree: e5a38bb703d4aeffddad6d9ab21026e3ab09616c
  1. bazel/
  2. build_overrides/
  3. buildtools/
  4. debian/
  5. docs/
  6. gn/
  7. include/
  8. infra/
  9. protos/
  10. src/
  11. test/
  12. tools/
  13. ui/
  14. .clang-format
  15. .gitignore
  16. .gn
  17. Android.bp
  18. Android.bp.extras
  19. BUILD
  20. BUILD.extras
  21. BUILD.gn
  22. codereview.settings
  23. heapprofd.rc
  24. MODULE_LICENSE_APACHE2
  25. NOTICE
  26. OWNERS
  27. perfetto.rc
  28. PRESUBMIT.py
  29. README.chromium
  30. README.md
  31. TEST_MAPPING
  32. WORKSPACE
README.md

Perfetto - Performance instrumentation and tracing

Perfetto is an open-source project for performance instrumentation and tracing of Linux/Android/Chrome platforms and user-space apps.

See www.perfetto.dev for docs.

Bugs

  • For bugs affecting Android or the tracing internals use the internal bug tracker (go/perfetto-bugs).
  • For bugs affecting Chrome use http://crbug.com, Component:Speed>Tracing label:Perfetto.