Ecosyste.ms: Issues

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

GitHub / dotnet/LLVMSharp issues and pull requests

#148 - ReplaceAllUsesWith is very slow

Issue - State: open - Opened by yowl about 4 years ago

#147 - Are there plans to support win-arm/win-arm64?

Issue - State: closed - Opened by alexrp about 4 years ago - 3 comments

#147 - Are there plans to support win-arm/win-arm64?

Issue - State: closed - Opened by alexrp about 4 years ago - 3 comments

#147 - Are there plans to support win-arm/win-arm64?

Issue - State: closed - Opened by alexrp about 4 years ago - 3 comments

#147 - Are there plans to support win-arm/win-arm64?

Issue - State: closed - Opened by alexrp about 4 years ago - 3 comments

#146 - Clarify LLVM release in README

Pull Request - State: closed - Opened by akoeplinger about 4 years ago - 1 comment

#146 - Clarify LLVM release in README

Pull Request - State: closed - Opened by akoeplinger about 4 years ago - 1 comment

#146 - Clarify LLVM release in README

Pull Request - State: closed - Opened by akoeplinger about 4 years ago - 1 comment

#146 - Clarify LLVM release in README

Pull Request - State: closed - Opened by akoeplinger about 4 years ago - 1 comment

#146 - Clarify LLVM release in README

Pull Request - State: closed - Opened by akoeplinger about 4 years ago - 1 comment

#145 - createLocalVariable not generated in LLVM.cs

Issue - State: closed - Opened by yowl about 4 years ago - 5 comments

#145 - createLocalVariable not generated in LLVM.cs

Issue - State: closed - Opened by yowl about 4 years ago - 5 comments

#145 - createLocalVariable not generated in LLVM.cs

Issue - State: closed - Opened by yowl about 4 years ago - 5 comments

#145 - createLocalVariable not generated in LLVM.cs

Issue - State: closed - Opened by yowl about 4 years ago - 5 comments

#145 - createLocalVariable not generated in LLVM.cs

Issue - State: closed - Opened by yowl about 4 years ago - 5 comments

#145 - createLocalVariable not generated in LLVM.cs

Issue - State: closed - Opened by yowl about 4 years ago - 5 comments

#144 - Expose Set/GetSubprogram on DIBuilderRef

Pull Request - State: closed - Opened by yowl about 4 years ago - 1 comment

#144 - Expose Set/GetSubprogram on DIBuilderRef

Pull Request - State: closed - Opened by yowl about 4 years ago - 1 comment

#144 - Expose Set/GetSubprogram on DIBuilderRef

Pull Request - State: closed - Opened by yowl about 4 years ago - 1 comment

#144 - Expose Set/GetSubprogram on DIBuilderRef

Pull Request - State: closed - Opened by yowl about 4 years ago - 1 comment

#144 - Expose Set/GetSubprogram on DIBuilderRef

Pull Request - State: closed - Opened by yowl about 4 years ago - 1 comment

#143 - 12.0.0-beta version please

Issue - State: closed - Opened by yowl about 4 years ago - 3 comments

#143 - 12.0.0-beta version please

Issue - State: closed - Opened by yowl about 4 years ago - 3 comments

#143 - 12.0.0-beta version please

Issue - State: closed - Opened by yowl about 4 years ago - 3 comments

#143 - 12.0.0-beta version please

Issue - State: closed - Opened by yowl about 4 years ago - 3 comments

#142 - LLVM.GetTargetFromTriple in OO api

Issue - State: open - Opened by lukechu10 about 4 years ago - 4 comments

#142 - LLVM.GetTargetFromTriple in OO api

Issue - State: open - Opened by lukechu10 about 4 years ago - 4 comments

#142 - LLVM.GetTargetFromTriple in OO api

Issue - State: open - Opened by lukechu10 about 4 years ago - 4 comments

#141 - Add methods for LLVMTargetDataRef

Pull Request - State: closed - Opened by yowl over 4 years ago - 6 comments

#141 - Add methods for LLVMTargetDataRef

Pull Request - State: closed - Opened by yowl over 4 years ago - 6 comments

#141 - Add methods for LLVMTargetDataRef

Pull Request - State: closed - Opened by yowl over 4 years ago - 6 comments

#141 - Add methods for LLVMTargetDataRef

Pull Request - State: closed - Opened by yowl over 4 years ago - 6 comments

#141 - Add methods for LLVMTargetDataRef

Pull Request - State: closed - Opened by yowl over 4 years ago - 6 comments

#140 - DataLayout class implementation

Issue - State: open - Opened by yowl over 4 years ago - 2 comments

#140 - DataLayout class implementation

Issue - State: open - Opened by yowl over 4 years ago - 2 comments

#140 - DataLayout class implementation

Issue - State: open - Opened by yowl over 4 years ago - 2 comments

#140 - DataLayout class implementation

Issue - State: open - Opened by yowl over 4 years ago - 2 comments

#140 - DataLayout class implementation

Issue - State: open - Opened by yowl over 4 years ago - 2 comments

#139 - String version of BuildMul(...) calls ReadOnlySpan<char> overload now

Pull Request - State: closed - Opened by TillAlex over 4 years ago - 2 comments

#139 - String version of BuildMul(...) calls ReadOnlySpan<char> overload now

Pull Request - State: closed - Opened by TillAlex over 4 years ago - 2 comments

#139 - String version of BuildMul(...) calls ReadOnlySpan<char> overload now

Pull Request - State: closed - Opened by TillAlex over 4 years ago - 2 comments

#139 - String version of BuildMul(...) calls ReadOnlySpan<char> overload now

Pull Request - State: closed - Opened by TillAlex over 4 years ago - 2 comments

#139 - String version of BuildMul(...) calls ReadOnlySpan<char> overload now

Pull Request - State: closed - Opened by TillAlex over 4 years ago - 2 comments

#138 - String version of BuildMul(...) calls itself instead of span overload

Issue - State: closed - Opened by TillAlex over 4 years ago - 1 comment

#138 - String version of BuildMul(...) calls itself instead of span overload

Issue - State: closed - Opened by TillAlex over 4 years ago - 1 comment

#138 - String version of BuildMul(...) calls itself instead of span overload

Issue - State: closed - Opened by TillAlex over 4 years ago - 1 comment

#138 - String version of BuildMul(...) calls itself instead of span overload

Issue - State: closed - Opened by TillAlex over 4 years ago - 1 comment

#138 - String version of BuildMul(...) calls itself instead of span overload

Issue - State: closed - Opened by TillAlex over 4 years ago - 1 comment

#137 - Add a proper managed wrapper for LLVMSharp

Pull Request - State: closed - Opened by tannergooding over 4 years ago - 4 comments

#137 - Add a proper managed wrapper for LLVMSharp

Pull Request - State: closed - Opened by tannergooding over 4 years ago - 4 comments

#137 - Add a proper managed wrapper for LLVMSharp

Pull Request - State: closed - Opened by tannergooding over 4 years ago - 4 comments

#137 - Add a proper managed wrapper for LLVMSharp

Pull Request - State: closed - Opened by tannergooding over 4 years ago - 4 comments

#135 - Ensure that LLVMTypeRef passes parameters down properly

Pull Request - State: closed - Opened by tannergooding over 4 years ago

#135 - Ensure that LLVMTypeRef passes parameters down properly

Pull Request - State: closed - Opened by tannergooding over 4 years ago

#135 - Ensure that LLVMTypeRef passes parameters down properly

Pull Request - State: closed - Opened by tannergooding over 4 years ago

#135 - Ensure that LLVMTypeRef passes parameters down properly

Pull Request - State: closed - Opened by tannergooding over 4 years ago

#133 - Print and read input functions with LLVMSharp

Issue - State: open - Opened by michalchecinski over 4 years ago - 1 comment

#132 - Adding a DllImport resolver for netcoreapp3.1

Pull Request - State: closed - Opened by tannergooding over 4 years ago

#132 - Adding a DllImport resolver for netcoreapp3.1

Pull Request - State: closed - Opened by tannergooding over 4 years ago

#132 - Adding a DllImport resolver for netcoreapp3.1

Pull Request - State: closed - Opened by tannergooding over 4 years ago

#132 - Adding a DllImport resolver for netcoreapp3.1

Pull Request - State: closed - Opened by tannergooding over 4 years ago

#132 - Adding a DllImport resolver for netcoreapp3.1

Pull Request - State: closed - Opened by tannergooding over 4 years ago

#129 - Was there any discussion around the removal of LLVMSharp.API?

Issue - State: open - Opened by ericsink over 4 years ago - 5 comments
Labels: question

#129 - Was there any discussion around the removal of LLVMSharp.API?

Issue - State: open - Opened by ericsink over 4 years ago - 5 comments
Labels: question

#129 - Was there any discussion around the removal of LLVMSharp.API?

Issue - State: open - Opened by ericsink over 4 years ago - 5 comments
Labels: question

#129 - Was there any discussion around the removal of LLVMSharp.API?

Issue - State: open - Opened by ericsink over 4 years ago - 5 comments
Labels: question

#122 - Add the missing RID specific packages for libLLVM 9.0.0

Issue - State: closed - Opened by tannergooding almost 5 years ago - 2 comments

#122 - Add the missing RID specific packages for libLLVM 9.0.0

Issue - State: closed - Opened by tannergooding almost 5 years ago - 2 comments

#122 - Add the missing RID specific packages for libLLVM 9.0.0

Issue - State: closed - Opened by tannergooding almost 5 years ago - 2 comments

#117 - Wrong libLLVM.so for linux-arm and linux-arm64

Issue - State: closed - Opened by TillAlex almost 5 years ago - 4 comments

#117 - Wrong libLLVM.so for linux-arm and linux-arm64

Issue - State: closed - Opened by TillAlex almost 5 years ago - 4 comments

#117 - Wrong libLLVM.so for linux-arm and linux-arm64

Issue - State: closed - Opened by TillAlex almost 5 years ago - 4 comments

#117 - Wrong libLLVM.so for linux-arm and linux-arm64

Issue - State: closed - Opened by TillAlex almost 5 years ago - 4 comments

#117 - Wrong libLLVM.so for linux-arm and linux-arm64

Issue - State: closed - Opened by TillAlex almost 5 years ago - 4 comments

#117 - Wrong libLLVM.so for linux-arm and linux-arm64

Issue - State: closed - Opened by TillAlex almost 5 years ago - 4 comments

#117 - Wrong libLLVM.so for linux-arm and linux-arm64

Issue - State: closed - Opened by TillAlex almost 5 years ago - 4 comments

#117 - Wrong libLLVM.so for linux-arm and linux-arm64

Issue - State: closed - Opened by TillAlex almost 5 years ago - 4 comments

#116 - Update to LLVM v9.0.0

Issue - State: closed - Opened by tannergooding about 5 years ago - 6 comments

#116 - Update to LLVM v9.0.0

Issue - State: closed - Opened by tannergooding about 5 years ago - 6 comments

#116 - Update to LLVM v9.0.0

Issue - State: closed - Opened by tannergooding about 5 years ago - 6 comments

#116 - Update to LLVM v9.0.0

Issue - State: closed - Opened by tannergooding about 5 years ago - 6 comments

#116 - Update to LLVM v9.0.0

Issue - State: closed - Opened by tannergooding about 5 years ago - 6 comments

#116 - Update to LLVM v9.0.0

Issue - State: closed - Opened by tannergooding about 5 years ago - 6 comments

#116 - Update to LLVM v9.0.0

Issue - State: closed - Opened by tannergooding about 5 years ago - 6 comments

#116 - Update to LLVM v9.0.0

Issue - State: closed - Opened by tannergooding about 5 years ago - 6 comments

#113 - ClangPInvokeGenerator Script is gone

Issue - State: closed - Opened by talyian about 5 years ago - 3 comments

#113 - ClangPInvokeGenerator Script is gone

Issue - State: closed - Opened by talyian about 5 years ago - 3 comments

#113 - ClangPInvokeGenerator Script is gone

Issue - State: closed - Opened by talyian about 5 years ago - 3 comments

#113 - ClangPInvokeGenerator Script is gone

Issue - State: closed - Opened by talyian about 5 years ago - 3 comments

#111 - [Question] Type checking and casting eg. [3 x i8] to i8*

Issue - State: closed - Opened by PaddiM8 about 5 years ago

#111 - [Question] Type checking and casting eg. [3 x i8] to i8*

Issue - State: closed - Opened by PaddiM8 about 5 years ago

#111 - [Question] Type checking and casting eg. [3 x i8] to i8*

Issue - State: closed - Opened by PaddiM8 about 5 years ago

#111 - [Question] Type checking and casting eg. [3 x i8] to i8*

Issue - State: closed - Opened by PaddiM8 about 5 years ago

#106 - LLVM.TargetMachineEmitToFile usage example

Issue - State: closed - Opened by moien007 about 5 years ago - 1 comment

#106 - LLVM.TargetMachineEmitToFile usage example

Issue - State: closed - Opened by moien007 about 5 years ago - 1 comment

#106 - LLVM.TargetMachineEmitToFile usage example

Issue - State: closed - Opened by moien007 about 5 years ago - 1 comment

#105 - Regenerate LLVMSharp using unsafe bindings.

Pull Request - State: closed - Opened by tannergooding over 5 years ago - 6 comments

#105 - Regenerate LLVMSharp using unsafe bindings.

Pull Request - State: closed - Opened by tannergooding over 5 years ago - 6 comments

#105 - Regenerate LLVMSharp using unsafe bindings.

Pull Request - State: closed - Opened by tannergooding over 5 years ago - 6 comments

#105 - Regenerate LLVMSharp using unsafe bindings.

Pull Request - State: closed - Opened by tannergooding over 5 years ago - 6 comments