You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Massive update to support LazyEncodedString Everywhere
* Not complete!
* This compiles the interop and wrapper libraries only, no impacted libs are updated yet.
* Completed changes with updates to consumers
* Includes additional testing
* More changes to support LazyEncodedString everywhere.
* Updated doc comments on `DisposeMEssageMarshaller type for clarity
* Attempting to work around problems in JIT on Windows x64.
* Apparently the JIT is assuming a 32 bit relocation as the default.
- See llvm/llvm-project#65641
* This adds support for JIT builder and, in particular, TargetMachineBuilder so that the CodeModel is explicit in children
* Static usings are now explicit everywhere they are needed.
- This removes static usings from the global usings.
* Additional support for LazyEncodedString
* Converted name of static class for LLVM-C interop `Error` for consistency
* Added marshaling form of `LLVMCreateStringError()`
* Added `LLVMErrorRef.CreateForNativeOut()`
- Eliminates need for annoying IDisposable warning suppression in many cases.
- This support out/return of native handle for reverse P/Invoke scenarios.
* Added setting the triple to the module transform for Kaleidoscope
- Ensures the triple is set and matches the JIT.
* Added `MarshalGCHandle.TryGet<>()` to support more intuitive acquisition of a managed context in native callbacks.
* Moved static factory for `ErrorInfo` to a constructor.
- Static factory was used for out/return to native but that causes a lot of suppression of warnings for dispose so isn't used. Instead, most APIs will use the static methods on LLVMErrorRef to report any errors. If the callback includes calling through a delegate, then it might use the constructor to build the resulting `ErrorInfo` to pass to native code.
* Updated version checks in interop code
* Since native API surface changed to support this build the version bump is needed
* Additional support for LazyEncodedString
* Added LibLLVMAttributeAllowedOn_All to make testing easier
* Changed signature of LibLLVMGetAttributeInfo to use an out param as the result instead of a raw pointer
- Wrapper layout is identical to the interop form so a simple cast through a pointer is all that is needed to "project"
* Doc comment updates/fixes
* [Build Fix] Corrected test
* Test file was removed locally and missed
- commit only included staged files so this edit and replace got in the way.
---------
Co-authored-by: smaillet <25911635+smaillet@users.noreply.github.com>
This template adds support to the syntax highlighting provided by [HightlightJS](https://highlightjs.readthedocs.io/en/latest/supported-languages.html).
3
-
The languages added are for ANTLR (Which seems bizarre it isn't already covered given the
4
-
esoteric nature of some of the supported languages...) and of course the `Kaleidoscope`
5
-
language, which was made up entirely for the purposes of LLVM tutorials. (No surprise that one
6
-
isn't supported) [Though it oddly IS supported directly in the [Local MarkDig
7
-
based editor](https://github.com/MadsKristensen/MarkdownEditor2022) used to edit these files...
3
+
The languages added are for ANTLR (Which seems bizarre it isn't already covered given
4
+
the esoteric nature of some of the supported languages...) and of course the `Kaleidoscope`
5
+
language, which was made up entirely for the purposes of LLVM tutorials. (No surprise that
6
+
one isn't supported) [Though it oddly IS supported directly in the [Local MarkDig based
7
+
editor](https://github.com/MadsKristensen/MarkdownEditor2022) used to edit these files...
8
8
9
+
## Theming
10
+
This template also updates the theme for SVG image backgrounds to improve readability
11
+
of the parse diagrams. It also updates the HighlightJS classifiers theming to better
12
+
show various parts of the ANTLR language.
13
+
14
+
The default theming is limited, especially for the ANTLR language, as it doesn't
15
+
support distinction between function definitions and invocations. (Both have
16
+
essentially the default text formatting so it's like none is applied). HighlightJS has
17
+
rather limited "scopes" and mapping to them for a language like ANTLR4 Lex/Grammar is
18
+
a challenge. It is NOT an imperative language (but it does generate to that) but the
0 commit comments