Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / nbp/holyjit issues and pull requests

#37 - Any updates on this project?

Issue - State: open - Opened by playXE over 4 years ago

#37 - Any updates on this project?

Issue - State: open - Opened by playXE over 4 years ago

#36 - Use holyjit on Windows?

Issue - State: open - Opened by CrABonzz over 4 years ago

#36 - Use holyjit on Windows?

Issue - State: open - Opened by CrABonzz over 4 years ago

#34 - Is HolyJit usable?

Issue - State: open - Opened by zaoqi over 4 years ago

#34 - Is HolyJit usable?

Issue - State: open - Opened by zaoqi over 4 years ago

#32 - Use luster as a benchmark (Lua VM)

Issue - State: open - Opened by zaoqi-unsafe over 5 years ago - 5 comments

#31 - Is the project dead?

Issue - State: closed - Opened by In-line over 5 years ago - 1 comment

#30 - LIR definition and Cranelift backend

Pull Request - State: open - Opened by nbp almost 6 years ago

#29 - Add a LIR format.

Issue - State: open - Opened by nbp about 6 years ago

#29 - Add a LIR format.

Issue - State: open - Opened by nbp about 6 years ago

#28 - Use Cranelift as a backend.

Issue - State: open - Opened by nbp about 6 years ago

#28 - Use Cranelift as a backend.

Issue - State: open - Opened by nbp about 6 years ago

#27 - Example command fails with Deserialize error

Issue - State: open - Opened by jonco3 over 6 years ago - 3 comments

#26 - Rust toolchain

Pull Request - State: closed - Opened by killercup over 6 years ago - 1 comment

#26 - Rust toolchain

Pull Request - State: closed - Opened by killercup over 6 years ago - 1 comment

#25 - Write LIR documentation explaining design constraints.

Issue - State: open - Opened by nbp over 6 years ago

#25 - Write LIR documentation explaining design constraints.

Issue - State: open - Opened by nbp over 6 years ago

#24 - Distribution as cargo binary on a "stable" version

Issue - State: closed - Opened by siriux over 6 years ago - 2 comments

#24 - Distribution as cargo binary on a "stable" version

Issue - State: closed - Opened by siriux over 6 years ago - 2 comments

#23 - Are there any alternatives to move holyjit forward on stable?

Issue - State: closed - Opened by siriux over 6 years ago - 5 comments

#23 - Are there any alternatives to move holyjit forward on stable?

Issue - State: closed - Opened by siriux over 6 years ago - 5 comments

#22 - About the future of this awesome project

Issue - State: closed - Opened by Hywan almost 7 years ago - 2 comments

#22 - About the future of this awesome project

Issue - State: closed - Opened by Hywan almost 7 years ago - 2 comments

#21 - Ideas and thoughts on runtime code optimization

Issue - State: closed - Opened by carli2 almost 7 years ago - 6 comments

#20 - Segfault inside Vec::index_mut call

Issue - State: open - Opened by mateon1 almost 7 years ago - 2 comments

#19 - Jitted code doesn't check if slice index is in bounds

Issue - State: open - Opened by mateon1 almost 7 years ago - 1 comment

#19 - Jitted code doesn't check if slice index is in bounds

Issue - State: open - Opened by mateon1 almost 7 years ago - 1 comment

#18 - Fix minor grammar issues in README.md

Pull Request - State: closed - Opened by jdanford almost 7 years ago - 1 comment

#17 - Lock dynasm version to 0.1.2

Pull Request - State: closed - Opened by jonas-schievink almost 7 years ago - 1 comment

#17 - Lock dynasm version to 0.1.2

Pull Request - State: closed - Opened by jonas-schievink almost 7 years ago - 1 comment

#16 - Fix loops and memory model of the Brainfuck interpreter.

Pull Request - State: closed - Opened by yblein almost 7 years ago - 3 comments

#15 - LLVM optimisations

Issue - State: closed - Opened by L-as almost 7 years ago - 1 comment

#14 - make it work with current rust

Issue - State: closed - Opened by fneddy almost 7 years ago - 12 comments

#14 - make it work with current rust

Issue - State: closed - Opened by fneddy almost 7 years ago - 12 comments

#13 - Suggestion: Small language implementations to test the holyjit features

Issue - State: closed - Opened by 6D65 almost 7 years ago - 1 comment

#12 - Question: Is the support for generating tracing JITs planned

Issue - State: closed - Opened by 6D65 almost 7 years ago - 1 comment

#12 - Question: Is the support for generating tracing JITs planned

Issue - State: closed - Opened by 6D65 almost 7 years ago - 1 comment

#11 - Brainfuck compiler is incorrect

Issue - State: closed - Opened by mateon1 almost 7 years ago - 2 comments

#11 - Brainfuck compiler is incorrect

Issue - State: closed - Opened by mateon1 almost 7 years ago - 2 comments

#10 - .

Issue - State: closed - Opened by adnam almost 7 years ago

#10 - .

Issue - State: closed - Opened by adnam almost 7 years ago

#9 - Use name consistently, fix one typo

Pull Request - State: closed - Opened by jgoldfar almost 7 years ago - 1 comment

#9 - Use name consistently, fix one typo

Pull Request - State: closed - Opened by jgoldfar almost 7 years ago - 1 comment

#8 - Offensive language

Issue - State: closed - Opened by jewsh almost 7 years ago - 3 comments

#7 - Is HolyJIT named after HolyC?

Issue - State: closed - Opened by tbodt almost 7 years ago - 2 comments

#7 - Is HolyJIT named after HolyC?

Issue - State: closed - Opened by tbodt almost 7 years ago - 2 comments

#6 - Grammar fixes; normalize "HolyJit" name in README

Pull Request - State: closed - Opened by yoasif almost 7 years ago - 1 comment

#5 - fix(typo): exhanged

Pull Request - State: closed - Opened by Freyskeyd almost 7 years ago - 1 comment

#4 - Fix(README) Typo in Readme example

Pull Request - State: closed - Opened by michfarr almost 7 years ago - 1 comment

#3 - README: "exhanged"

Issue - State: closed - Opened by floatingatoll almost 7 years ago

#2 - Fix typo

Pull Request - State: closed - Opened by badboy almost 7 years ago - 1 comment

#1 - fix(readme) Fix a typo

Pull Request - State: closed - Opened by Hywan almost 7 years ago - 1 comment