mirror of
https://github.com/shadps4-emu/shadPS4.git
synced 2026-04-26 00:05:58 +03:00
[PR #1587] [MERGED] recompiler: fix how srt pass handles step rate sharps in special case #2182
Labels
No labels
Bloodborne
bug
contributor wanted
documentation
enhancement
frontend
good first issue
help wanted
linux
pull-request
question
release
verification progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/shadPS4#2182
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/shadps4-emu/shadPS4/pull/1587
Author: @baggins183
Created: 11/24/2024
Status: ✅ Merged
Merged: 11/24/2024
Merged by: @psucien
Base:
main← Head:srt-step-rate-fix📝 Commits (1)
3a89ec3recompiler: fix how srt pass handles step rate sharps in special case📊 Changes
1 file changed (+7 additions, -3 deletions)
View changed files
📝
src/shader_recompiler/ir/passes/flatten_extended_userdata_pass.cpp(+7 -3)📄 Description
In the SRT code path there has to be special handling for step rate buffers read inside the fetch shader because fetch shaders aren't actually recompiled.
The original SRT commit handled step rate buffers by making a "reservation" in the flattened user data buffer when a sharp was found during fetch shader parsing, which the JIT program would fill in.
The bug is that r10d (32 bit) was used to hold the indirect pointer used to find the step rate V#. Generalize by using Push/PopPtr to put the ptr in %rdi which also mask off the high ptr bits like Info::ReadUdReg
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.