|
Upcoming Events
#cal-summary
osl-dev@... Upcoming Events OSL TSC meeting ( every other week )
When:
Thursday, December 22, 2022, 2:00pm to 3:00pm
(GMT-08:00) America/Los
osl-dev@... Upcoming Events OSL TSC meeting ( every other week )
When:
Thursday, December 22, 2022, 2:00pm to 3:00pm
(GMT-08:00) America/Los
|
By
Group Notification <noreply@...>
·
#5063
·
|
|
Now: OSL TSC meeting ( every other week ) - Thursday, December 8, 2022
#cal-notice
OSL TSC meeting ( every other week )
When:
Thursday, December 8, 2022
2:00pm to 3:00pm
(UTC-08:00) America/Los Angeles
Where:
https://zoom.us/j/100511909
Organizer: Chris
OSL TSC meeting ( every other week )
When:
Thursday, December 8, 2022
2:00pm to 3:00pm
(UTC-08:00) America/Los Angeles
Where:
https://zoom.us/j/100511909
Organizer: Chris
|
By
Group Notification <noreply@...>
·
#5062
·
|
|
Event: OSL TSC meeting ( every other week ) - Thursday, December 8, 2022
#cal-reminder
Reminder: OSL TSC meeting ( every other week )
When:
Thursday, December 8, 2022
2:00pm to 3:00pm
(UTC-08:00) America/Los Angeles
Where:
https://zoom.us/j/100511909
Organizer: Chris
Reminder: OSL TSC meeting ( every other week )
When:
Thursday, December 8, 2022
2:00pm to 3:00pm
(UTC-08:00) America/Los Angeles
Where:
https://zoom.us/j/100511909
Organizer: Chris
|
By
Group Notification <noreply@...>
·
#5061
·
|
|
Event: OSL TSC meeting ( every other week ) - Thursday, December 8, 2022
#cal-reminder
Reminder: OSL TSC meeting ( every other week )
When:
Thursday, December 8, 2022
2:00pm to 3:00pm
(UTC-08:00) America/Los Angeles
Where:
https://zoom.us/j/100511909
Organizer: Chris
Reminder: OSL TSC meeting ( every other week )
When:
Thursday, December 8, 2022
2:00pm to 3:00pm
(UTC-08:00) America/Los Angeles
Where:
https://zoom.us/j/100511909
Organizer: Chris
|
By
Group Notification <noreply@...>
·
#5060
·
|
|
Event: OSL TSC meeting ( every other week ) - Thursday, December 8, 2022
#cal-reminder
Reminder: OSL TSC meeting ( every other week )
When:
Thursday, December 8, 2022
2:00pm to 3:00pm
(UTC-08:00) America/Los Angeles
Where:
https://zoom.us/j/100511909
Organizer: Chris
Reminder: OSL TSC meeting ( every other week )
When:
Thursday, December 8, 2022
2:00pm to 3:00pm
(UTC-08:00) America/Los Angeles
Where:
https://zoom.us/j/100511909
Organizer: Chris
|
By
Group Notification <noreply@...>
·
#5059
·
|
|
Release: OSL v1.12.7.1
We have tagged v1.12.7.1 as the latest production release and moved the
"release" branch marker to that point. This is guaranteed to be API,
ABI, and link back-compatible with prior 1.12 releases.
We have tagged v1.12.7.1 as the latest production release and moved the
"release" branch marker to that point. This is guaranteed to be API,
ABI, and link back-compatible with prior 1.12 releases.
|
By
Larry Gritz
·
#5058
·
|
|
Upcoming Events
#cal-summary
osl-dev@... Upcoming Events OSL TSC meeting ( every other week )
When:
Thursday, December 8, 2022, 2:00pm to 3:00pm
(GMT-08:00) America/Los
osl-dev@... Upcoming Events OSL TSC meeting ( every other week )
When:
Thursday, December 8, 2022, 2:00pm to 3:00pm
(GMT-08:00) America/Los
|
By
Group Notification <noreply@...>
·
#5057
·
|
|
Event: OSL TSC meeting ( every other week ) - Thursday, December 8, 2022
#cal-reminder
Reminder: OSL TSC meeting ( every other week )
When:
Thursday, December 8, 2022
2:00pm to 3:00pm
(UTC-08:00) America/Los Angeles
Where:
https://zoom.us/j/100511909
Organizer: Chris
Reminder: OSL TSC meeting ( every other week )
When:
Thursday, December 8, 2022
2:00pm to 3:00pm
(UTC-08:00) America/Los Angeles
Where:
https://zoom.us/j/100511909
Organizer: Chris
|
By
Group Notification <noreply@...>
·
#5056
·
|
|
Upcoming Events
#cal-summary
osl-dev@... Upcoming Events OSL TSC meeting ( every other week )
When:
Thursday, December 8, 2022, 2:00pm to 3:00pm
(GMT-08:00) America/Los
osl-dev@... Upcoming Events OSL TSC meeting ( every other week )
When:
Thursday, December 8, 2022, 2:00pm to 3:00pm
(GMT-08:00) America/Los
|
By
Group Notification <noreply@...>
·
#5055
·
|
|
No TSC meeting this week
Reminder that this Thursday's scheduled OSL TSC meeting is cancelled because it falls on US Thanksgiving holiday, lots of members will be on vacation this week.
-- lg
--
Larry
Reminder that this Thursday's scheduled OSL TSC meeting is cancelled because it falls on US Thanksgiving holiday, lots of members will be on vacation this week.
-- lg
--
Larry
|
By
Larry Gritz
·
#5054
·
|
|
Upcoming Events
#cal-summary
osl-dev@... Upcoming Events OSL TSC meeting ( every other week )
When:
Thursday, December 8, 2022, 2:00pm to 3:00pm
(GMT-08:00) America/Los
osl-dev@... Upcoming Events OSL TSC meeting ( every other week )
When:
Thursday, December 8, 2022, 2:00pm to 3:00pm
(GMT-08:00) America/Los
|
By
Group Notification <noreply@...>
·
#5053
·
|
|
Re: Varying Closure Keyword Parameters Not Being Correctly Evaluated During Batched Execution?
( Apologies again to Stephen for accidentally double-posting as reply-to-sender ... )
I've put up a PR with this fix here: https://github.com/AcademySoftwareFoundation/OpenShadingLanguage/pull/1620
( Apologies again to Stephen for accidentally double-posting as reply-to-sender ... )
I've put up a PR with this fix here: https://github.com/AcademySoftwareFoundation/OpenShadingLanguage/pull/1620
|
By
dresserd@...
·
#5052
·
|
|
Re: Varying Closure Keyword Parameters Not Being Correctly Evaluated During Batched Execution?
Ahh, yes, you're right -- that's more complicated than the copy we have locally. That extra complication is to deal with parameters that are arrays, and translating from SOA back to the AOS layout of
Ahh, yes, you're right -- that's more complicated than the copy we have locally. That extra complication is to deal with parameters that are arrays, and translating from SOA back to the AOS layout of
|
By
Stephen Friedman
·
#5051
·
|
|
Re: Varying Closure Keyword Parameters Not Being Correctly Evaluated During Batched Execution?
Hmm, this is a bit more complex than what you're describing, because the batched_llvm_gen version of llvm_gen_closure doesn't just switch the target of the memcpy, it replaces the memcpy completely
Hmm, this is a bit more complex than what you're describing, because the batched_llvm_gen version of llvm_gen_closure doesn't just switch the target of the memcpy, it replaces the memcpy completely
|
By
dresserd@...
·
#5050
·
|
|
Re: Varying Closure Keyword Parameters Not Being Correctly Evaluated During Batched Execution?
Yeah, that looks like I just "missed a spot" -- it turns out while we use keyword args, in our renderer, they've only ever been uniform across the batch so I didn't catch it.
I don't have the cycles
Yeah, that looks like I just "missed a spot" -- it turns out while we use keyword args, in our renderer, they've only ever been uniform across the batch so I didn't catch it.
I don't have the cycles
|
By
Stephen Friedman
·
#5049
·
|
|
Re: Varying Closure Keyword Parameters Not Being Correctly Evaluated During Batched Execution?
Since I've now got a clean repro independent of my code, I went ahead and made an issue: https://github.com/AcademySoftwareFoundation/OpenShadingLanguage/issues/1619
-Daniel
Since I've now got a clean repro independent of my code, I went ahead and made an issue: https://github.com/AcademySoftwareFoundation/OpenShadingLanguage/issues/1619
-Daniel
|
By
dresserd@...
·
#5048
·
|
|
Re: Varying Closure Keyword Parameters Not Being Correctly Evaluated During Batched Execution?
Oops, I just wrote up a nice reply to Stephen in the web UI, and then accidentally hit the big "Reply to Author" button instead of the little "Group Reply" button. For the benefit of anyone else
Oops, I just wrote up a nice reply to Stephen in the web UI, and then accidentally hit the big "Reply to Author" button instead of the little "Group Reply" button. For the benefit of anyone else
|
By
dresserd@...
·
#5047
·
|
|
Re: Varying Closure Keyword Parameters Not Being Correctly Evaluated During Batched Execution?
The intent was that if you had an existing method to parse the closure and decide what to do with them, you could just call that in a loop -- that's what our renderer does, and we've used something
The intent was that if you had an existing method to parse the closure and decide what to do with them, you could just call that in a loop -- that's what our renderer does, and we've used something
|
By
Stephen Friedman
·
#5046
·
|
|
Upcoming Events
#cal-summary
osl-dev@... Upcoming Events OSL TSC meeting ( every other week )
When:
Thursday, December 8, 2022, 2:00pm to 3:00pm
(GMT-08:00) America/Los
osl-dev@... Upcoming Events OSL TSC meeting ( every other week )
When:
Thursday, December 8, 2022, 2:00pm to 3:00pm
(GMT-08:00) America/Los
|
By
Group Notification <noreply@...>
·
#5045
·
|
|
Varying Closure Keyword Parameters Not Being Correctly Evaluated During Batched Execution?
I've gotten around to trying out the exciting new OSL batched execution mode for Gaffer.
For context, Gaffer's internal use of OSL is a bit atypical - we're not a renderer, but we offer OSL for
I've gotten around to trying out the exciting new OSL batched execution mode for Gaffer.
For context, Gaffer's internal use of OSL is a bit atypical - we're not a renderer, but we offer OSL for
|
By
dresserd@...
·
#5044
·
|