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

Compile and link source in program class #11

Closed
ProGTX opened this issue Jun 6, 2015 · 3 comments
Closed

Compile and link source in program class #11

ProGTX opened this issue Jun 6, 2015 · 3 comments

Comments

@ProGTX
Copy link
Owner

ProGTX commented Jun 6, 2015

No description provided.

@ProGTX
Copy link
Owner Author

ProGTX commented Sep 29, 2015

Related: #12.

@ProGTX
Copy link
Owner Author

ProGTX commented Oct 10, 2015

A lot needed to be done.

  • A lot of changes in 063cc7e, which brought compilation to kernel class, but also broke a lot. The main issue was that breaking the build process into compile and link parts broke the queue order.
  • Very important fix in 6d54e79 to address the wrong enqueue order - the kernel wasn't initialized at the proper time.
  • Last touches on linking in 0bfef95.
  • Mostly working at a70e28a.
  • However, only id class was treated as a device reference, but range should also have been.
  • Created a new superclass for both of these classes in 10912d0 -> point_ref class. This also allowed proper passing of ids and ranges to kernels.
  • point_ref was mostly done (to cover the current tests) in da721ef.

A lot still needs to be done here, but for now it's mostly working.

@ProGTX ProGTX closed this as completed Oct 10, 2015
@ProGTX
Copy link
Owner Author

ProGTX commented Oct 10, 2015

A nice side effect of the point_ref class is that it implements a lot of the functionality needed for #2. Vector types may be migrated at some point to use it. However, the point_ref class has a huge overhead and should not be used much in user code - evidenced by the speedup gained by 1736a8d.

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

No branches or pull requests

1 participant