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

Get new GC in LuaJIT upstream #3

Open
DemiMarie opened this issue Oct 29, 2016 · 3 comments
Open

Get new GC in LuaJIT upstream #3

DemiMarie opened this issue Oct 29, 2016 · 3 comments

Comments

@DemiMarie
Copy link

It would be very useful to get the new GC upstreamed.

@fsfod
Copy link
Owner

fsfod commented Oct 29, 2016

It still missing lots of things and I got no reply from Mike Paul when I emailed him months ago

@lukego
Copy link

lukego commented Nov 2, 2016

Seems like we need to create a new upstream branch, right? Mike is maintaining master and v2.1 but these are both in feature-freeze and so somebody needs to maintain a new branch that accepts new features (v2.2, v3.0, etc).

I would be quite willing to do the branch-maintaining part of the work. For example I could maintain a branch that adopts a new GC once both @fsfod and @corsix are happy with the implementation and when it passes all available tests (I can use CI to verify LuaJIT suite, LuaJIT benchmarks, Snabb benchmarks, anything else that is available.)

This would only work on the assumption that the GC implementation does not require input from Mike and that @fsfod and @corsix see eye to eye on the implementation...?

@DemiMarie
Copy link
Author

@lukego I agree. v2.1 did get an ARM64 JIT backend and fixed trace stitching, but that seems to be it.

Mike Pall has been looking for a maintainer for over a year. Are you stepping up to the plate?

fsfod pushed a commit that referenced this issue Nov 22, 2017
Setup travisci to run the luajit test suite
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

3 participants