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
  • tests
  • compiler_tests
  • ShaderValidation_test.cpp
Find file
BlameHistoryPermalink
  • Olli Etuaho's avatar
    Fix accessing the name of a nested struct definition · f095799b
    Olli Etuaho authored Dec 22, 2017
    When generating an error message about the struct nesting limit, the
    code should make sure that the struct definitions are not nested.
    While nested struct definitions by themselves are also an error,
    they're not a syntax error so parsing will continue after encountering
    them.
    
    This fixes a regression from commit: Don't allocate name strings for
    empty symbols.
    
    BUG=chromium:797156
    TEST=angle_unittests
    
    Change-Id: I4149fbe874c0e7ec90e690aec078ccaf7313eab0
    Reviewed-on: https://chromium-review.googlesource.com/842643
    Commit-Queue: Olli Etuaho <oetuaho@nvidia.com>
    Reviewed-by: 's avatarJamie Madill <jmadill@chromium.org>
    f095799b
ShaderValidation_test.cpp 169 KB
EditWeb IDE
×

Replace ShaderValidation_test.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.