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

asymmetry for userdata vs attributes with ShadingSystemImpl::getattribute #1622

Open
etheory opened this issue Nov 18, 2022 · 0 comments
Open

Comments

@etheory
Copy link
Contributor

etheory commented Nov 18, 2022

Problem

In

ShadingSystemImpl::getattribute(ShaderGroup* group, string_view name,
we have:

  • num_userdata
  • userdata_names
  • userdata_types
  • userdata_offsets
  • userdata_derivs

but only:

  • num_attributes_needed
  • attributes_needed
  • attribute_scopes
  • unknown_attributes_needed

which is missing a types, offsets and derivs for attributes.

This issue is to log the need for parity across these.

The mis-matching names are already a little bit confusing, so some kind of homogenization would also make sense.

Expected behavior:

I expect userdata and attributes to provide the same abilities for query during llvm compilation.

Actual behavior:

I don't have parity for userdata and attribute queries.

Steps to Reproduce

NA

Versions

  • OSL branch/version: ALL
  • OS: ALL
  • C++ compiler: ALL
  • LLVM version: ALL
  • OIIO version: ALL

NOTE

I know this should be a PR, which I'll try and get to, but for the moment, I figured an issue would make sense.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant