Implement new extension API to support Alloca with addresspace.#73
Merged
smaillet merged 1 commit intoUbiquityDotNET:developfrom Dec 6, 2025
Merged
Conversation
* This allow generators using address spaces to directly support allocas with a different address space ID. The actual address won't change but it is usable to indicate that
an allocation results in a value valid for an address space. This is normally used for runtimes that support some sort of GC/managed reference vs a native pointer. It is useful to distinguish the intended use and that the address space is part of the type of the pointer (even if it is OPAQUE).
* Cleaned up some headers
- Minor re-formatting
- Protected wrappers for `<cstdint>` and `<climits>` as those are not formally available for ISO/C compilation.
- While it is increasingly rare to use a pure C compilation it is plausible and should still be supported.
smaillet
added a commit
to smaillet/Llvm.NET
that referenced
this pull request
Dec 6, 2025
* Such is the problem of per line staging of a file while withholding some changes. * InstructionBuilder has some local changes waiting on a release of [new extension API support](UbiquityDotNET/Llvm.Libs#73) but other chanes were supposed to be included [Sigh...] - Sadly, InstructionBuilder has no formal testing (relies on samples) so this new instruction has no tests.
smaillet
added a commit
to UbiquityDotNET/Llvm.NET
that referenced
this pull request
Dec 6, 2025
* Such is the problem of per line staging of a file while withholding some changes. * InstructionBuilder has some local changes waiting on a release of [new extension API support](UbiquityDotNET/Llvm.Libs#73) but other chanes were supposed to be included [Sigh...] - Sadly, InstructionBuilder has no formal testing (relies on samples) so this new instruction has no tests.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Implement new extension API to support Alloca with addresspace.
an allocation results in a value valid for an address space. This is normally used for runtimes that support some sort of GC/managed reference vs a native pointer. It is useful to distinguish the intended use and that the address space is part of the type of the pointer (even if it is OPAQUE).
<cstdint>and<climits>as those are not formally available for ISO/C compilation.