Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
S
swiftshader
  • 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
  • swiftshader
  • Repository

Switch branch/tag
  • swiftshader
  • tests
  • unittests
  • unittests.vcxproj.user
Find file
BlameHistoryPermalink
  • Nicolas Capens's avatar
    Prevent 32-bit numeric overflow on image allocation. · 607771b4
    Nicolas Capens authored May 08, 2018
    We assume the pixels of an image can be addressed with a signed 32-bit
    offset, including any padding. For a 3D image it's possible to exceed
    this without exceeding the per-dimension limits. Lowering the per-
    dimension limit so the allocation is always less than 2 GiB makes them
    unreasonably small, so instead we must check the total size.
    
    Use 1 GiB as the soft limit in OpenGL.
    
    Bug chromium:835299
    
    Change-Id: I9c5184002c1710e3923b549f8c21e7f6a516e1c7
    Reviewed-on: https://swiftshader-review.googlesource.com/18869Reviewed-by: 's avatarNicolas Capens <nicolascapens@google.com>
    Tested-by: 's avatarNicolas Capens <nicolascapens@google.com>
    607771b4
unittests.vcxproj.user 1.39 KB
EditWeb IDE
×

Replace unittests.vcxproj.user

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.