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.

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

internal/shader: some assignment operators didn't work correctly #3140

Closed
11 tasks
hajimehoshi opened this issue Oct 21, 2024 · 0 comments
Closed
11 tasks

internal/shader: some assignment operators didn't work correctly #3140

hajimehoshi opened this issue Oct 21, 2024 · 0 comments
Labels
Milestone

Comments

@hajimehoshi
Copy link
Owner

Ebitengine Version

366f489

Operating System

  • Windows
  • macOS
  • Linux
  • FreeBSD
  • OpenBSD
  • Android
  • iOS
  • Nintendo Switch
  • PlayStation 5
  • Xbox
  • Web Browsers

Go Version (go version)

go version go1.23.1 darwin/arm64

What steps will reproduce the problem?

Run this test in the ebiten package:

func TestShaderCompile(t *testing.T) {
	if _, err := ebiten.NewShader([]byte(`//kage:unit pixels

package main

func Fragment(dstPos vec4, srcPos vec2, color vec4) vec4 {
	x := 0
	x ^= x
	return vec4(0)
}
`)); err != nil {
		t.Fatal(err)
	}
}

What is the expected result?

The test passes

What happens instead?

The test fails:

--- FAIL: TestShaderCompile (0.00s)
    shader_test.go:2833: graphics: vertex shader entry point '__vertex' is missing
FAIL
FAIL    github.com/hajimehoshi/ebiten/v2        0.550s
FAIL

Anything else you feel useful to add?

No response

@hajimehoshi hajimehoshi added this to the v2.8.2 milestone Oct 21, 2024
@hajimehoshi hajimehoshi changed the title internal/shader: The operator ^= causes mysterious error internal/shader: some assignment operators didn't work correctly Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant