Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

OpPhi's incoming basic block ... is not a predecessor of ... #13

Open
FROL256 opened this issue Jan 27, 2021 · 2 comments
Open

OpPhi's incoming basic block ... is not a predecessor of ... #13

FROL256 opened this issue Jan 27, 2021 · 2 comments

Comments

@FROL256
Copy link

FROL256 commented Jan 27, 2021

  1. The source code to reproduce the bug: https://drive.google.com/file/d/1HaSsqCharKF2mdg8wMA6IrPDwy3fL848/view?usp=sharing

  2. The error from validation layer:

UNASSIGNED-CoreValidation-Shader-InconsistentSpirv(ERROR / SPEC): msgNum: 7060244 - Validation Error: [ UNASSIGNED-CoreValidation-Shader-InconsistentSpirv ] Object 0: handle = 0x555555c61e28, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0x6bbb14 | SPIR-V module not valid: OpPhi's incoming basic block <id> 187[%187] is not a predecessor of <id> 279[%279].
  %297 = OpPhi %bool %false %187 %295 %280
  1. Seems the problem is inside "RaySphereHit" function, but it is quite simple.

Would be happy if you could look at this, many thanks!
@seanbaxter
Copy link
Owner

It's a known structurization problem I have. Will make another attempt to fix it soon.

@FROL256
Copy link
Author

FROL256 commented Feb 5, 2021

That's great, thank you very much! I will report more bugs with the new release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@seanbaxter @FROL256