Skip to content

[HLSL] Investigate whether we can avoid memset and memcpy in object construction and type casting #138788

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

Open
bogner opened this issue May 7, 2025 · 0 comments
Labels
HLSL HLSL Language Support

Comments

@bogner
Copy link
Contributor

bogner commented May 7, 2025

Clang's codegen for C++ constructors doesn't seem to check the target for whether we should generate memcpy for members, and there are also memcpys generated for certain types of cast. We should investigate whether this can and should be made target specific (Especially after #138787), and if so we can eliminate DXIL's custom legalization of memset and avoid implementing memcpy legalization.

@bogner bogner added the HLSL HLSL Language Support label May 7, 2025
@damyanp damyanp moved this to Ready in HLSL Support May 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
HLSL HLSL Language Support
Projects
Status: Ready
Development

No branches or pull requests

1 participant