Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
A
angle
  • Project
    • Overview
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Chen Yisong
  • angle
  • Repository

Switch branch/tag
  • angle
  • src
  • common
  • debug.cpp
Find file
BlameHistoryPermalink
  • Ian Elliott's avatar
    Add run-time check in EVENT() to disable debug markers · e89c8f7c
    Ian Elliott authored Oct 22, 2020
    To avoid a large performance impact from adding Vulkan debug-util
    markers for every GLES entrypoint, the EVENT() macro needs a run-time
    check that avoids constructing a ScopedPerfEventHelper object.
    
    Test: angle_perftests -v --local-output --gtest_filter="TracePerfTest.Run/*nba*"
    Bug: b/170249632
    Change-Id: I422111cdf6f6f713800e7ac587e66582bd00359f
    Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2491009
    Commit-Queue: Ian Elliott <ianelliott@google.com>
    Reviewed-by: 's avatarShahbaz Youssefi <syoussefi@chromium.org>
    Reviewed-by: 's avatarJamie Madill <jmadill@chromium.org>
    e89c8f7c
debug.cpp 8.26 KB
EditWeb IDE
×

Replace debug.cpp

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.