-
Notifications
You must be signed in to change notification settings - Fork 2.1k
building altivec support on ppc64e results in color corruption in end products #3428
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.
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
Labels
waiting
Waiting on user response
Comments
JeremyRand
pushed a commit
to JeremyRand/SDL
that referenced
this issue
May 6, 2023
An in-place swizzle mutation was erroneously inside of a loop, which caused each consecutive 4-pixel vector to alternate between correct and incorrect endianness. The bug was introduced in 715e070. Thanks to RobbieAB for reporting the bug. Fixes libsdl-org#3428
JeremyRand
pushed a commit
to JeremyRand/SDL
that referenced
this issue
May 6, 2023
An in-place swizzle mutation was erroneously inside of a loop, which caused each consecutive 4-pixel vector to alternate between correct and incorrect endianness. The bug was introduced in 715e070. Thanks to RobbieAB for reporting the bug. Fixes libsdl-org#3428
JeremyRand
pushed a commit
to JeremyRand/SDL
that referenced
this issue
May 6, 2023
An in-place swizzle mutation was erroneously inside of a loop, which caused each consecutive 4-pixel vector to alternate between correct and incorrect endianness. The bug was introduced in 715e070. Thanks to RobbieAB for reporting the bug. Fixes libsdl-org#3428
sezero
pushed a commit
to libsdl-org/SDL-1.2
that referenced
this issue
May 6, 2023
An in-place swizzle mutation was erroneously inside of a loop, which caused each consecutive 4-pixel vector to alternate between correct and incorrect endianness. The bug was introduced in libsdl-org/SDL@715e070 (77a2237). Thanks to RobbieAB for reporting the bug. Fixes libsdl-org/SDL#3428 (cherry picked from commit libsdl-org/SDL@9142292)
icculus
pushed a commit
to icculus/SDL
that referenced
this issue
May 12, 2023
An in-place swizzle mutation was erroneously inside of a loop, which caused each consecutive 4-pixel vector to alternate between correct and incorrect endianness. The bug was introduced in 715e070. Thanks to RobbieAB for reporting the bug. Fixes libsdl-org#3428
sezero
pushed a commit
to sezero/SDL
that referenced
this issue
May 17, 2023
An in-place swizzle mutation was erroneously inside of a loop, which caused each consecutive 4-pixel vector to alternate between correct and incorrect endianness. The bug was introduced in 715e070. Thanks to RobbieAB for reporting the bug. Fixes libsdl-org#3428 (cherry picked from commit 9142292)
lexi-the-cute
pushed a commit
to lexi-the-cute/SDL
that referenced
this issue
May 22, 2023
An in-place swizzle mutation was erroneously inside of a loop, which caused each consecutive 4-pixel vector to alternate between correct and incorrect endianness. The bug was introduced in 715e070. Thanks to RobbieAB for reporting the bug. Fixes libsdl-org#3428 (cherry picked from commit 9142292)
mikrosk
pushed a commit
to mikrosk/SDL-1.2
that referenced
this issue
Dec 21, 2023
An in-place swizzle mutation was erroneously inside of a loop, which caused each consecutive 4-pixel vector to alternate between correct and incorrect endianness. The bug was introduced in libsdl-org/SDL@715e070 (libsdl-org@77a2237). Thanks to RobbieAB for reporting the bug. Fixes libsdl-org/SDL#3428 (cherry picked from commit libsdl-org/SDL@9142292)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This bug report was migrated from our old Bugzilla tracker.
Reported in version: 2.0.10
Reported for operating system, platform: Linux, PowerPC
Comments on the original bug report:
On 2019-10-20 12:36:38 +0000, wrote:
On 2019-10-20 14:10:36 +0000, Ozkan Sezer wrote:
On 2019-10-23 08:51:53 +0000, wrote:
On 2019-12-01 23:59:13 +0000, wrote:
On 2019-12-02 00:17:34 +0000, Ozkan Sezer wrote:
On 2019-12-02 00:41:34 +0000, wrote:
On 2019-12-04 06:13:58 +0000, Sam Lantinga wrote:
On 2019-12-04 18:53:20 +0000, Ryan C. Gordon wrote:
On 2019-12-04 22:53:30 +0000, wrote:
The text was updated successfully, but these errors were encountered: