-
Notifications
You must be signed in to change notification settings - Fork 22
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
rtc_boids and other profiling changes #371
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
So much got added to this branch than intended. Not sure if we want to keep the __ldg change (but I think removing it will also require reverting 48b863). Otherwise it seems mergeable. |
ptheywood
reviewed
Oct 12, 2020
Robadob
changed the title
rtc_example is now rtc_boids_bruteforce
rtc_boids and other profiling changes
Oct 13, 2020
Robadob
force-pushed
the
boids_rtc
branch
3 times, most recently
from
October 16, 2020 15:44
d9c7273
to
efa0d9e
Compare
Remove device new for FLAME GPU API for agent functions and agent function conditions Add curve get via __ldg() function. Pass additional flags to RTC compilation Add CMake option to log dynamic RTC files to disk at runtime
CURVE device methods set/get variable methods are now seperated into agent, message in, message out, new agent. When executing non-rtc code, these forward to the previous set/get variable methods. Under RTC however they go to specific methods, this allows variable accesses to be optimised away to direct memory reads at compile time.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This branch started out as adding an rtc version of boids but has grown, so I've compiled a changelog.
Changelog:
boids_rtc_bruteforce
andboids_rtc_spatial3D
examples, these models are identical to their non-rtc variants.rtc_example
new
anddelete
fromagent_function_wrapper
andagent_function_condition_wrapper
, api object is now allocated in local not global.getVariableByHash_ldg()
andgetVariable_ldg()
to CURVE. These are used by message bruteforce (also affects RTC curve header).EXPORT_RTC_SOURCES
. If enabled, this sets the macroOUTPUT_RTC_DYNAMIC_FILES
causing RTC dynamic files to be exported to the working directory at runtime.end()
iterator for spatial messaging to reduce instructions on comparison.Normal tests pass on Windows (seatbelts on).
Normal tests pass on Linux (Petes machine, seatbelts on/off).
Swig tests pass on Windows (seatbelts on)
Normal tests fail on Mavericks. All tests failing are environment, not sure why.