Sync with upstream #12
Merged
Conversation
This file contains 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
* Fix incorrect build instructions for Windows * Add link to Visual Studio installer * Refine building instructions for VS2019+
* Minor code refactoring for re-use. * Add Class.FindVariable helper method. * Upgrade to .NET 6.
* Minor code refactorings. * Fix debug assert issue with vtable methods. * Add support for WebAssembly C++ ABI to parser and AST converter.
* Code cleanups. * Run GetterSetterToPropertyPass for more generators. * Fixed compile warning when compiling parser bindings. * Cleanup driver code. * Remove dead 32-bit code. * Reduce verbosity when Options.Quiet is set. * Remove test compile-time warnings. * Move .NET tests to tests/dotnet. * Remove unused AST viewer code and premake-qt submodule. * Move tests2/ contents to tests/.
This is to workaround MSBuild CMake step from LLVM build in Windows picking this up.
…dLogicalOriginalName (mono#1740) Fixed properties getters of QualifiedOriginalName, QualifiedLogicalOriginalName and methods GetQualifiedName(), GatherNamespaces.
Wrap default parameter expressions in parentheses to ensure whole expressions are casted instead of only the first operand.
Remove Gitter since the link is 404 and we have not been using it anyway.
* CSharpExpressionPrinter: Recurse into operands Recursively call `VisitExpression` on the LHS and RHS of a binary operator expression. This fixes the generation for complex default parameters involving things other than two enumeration members. * CSharpSources: Use `const` when possible Generate `const` instead of `static` members when possible. This allows generated members to be used when compile-time constants are required, such as default parameters.
- Expression generation for `ConstructorReference` now also recursively calls `VisitExpression` for the argument if only one argument is detected. This allows correct overload generation for functions taking a variable as the default parameter value. - Default parameters of pointer-to-enumeration types are now correctly generated similar to primitive types.
* Generator: Customization for const char[] Allow the user to choose whether `const char[]` should be marshalled as `string` or a normal `char` array in C#. A new option `MarshalConstCharArrayAsString` is added, and is `true` by default. This helps in situations where the original C++ API distinguishes between C-strings and char arrays using the two different notations. * CSharpMarshal: Fix unknown length array marshal For unknown length arrays, also run a conversion loop if the primitive type encountered needs conversion (e.g. `char` to `sbyte`). * CSharpTypePrinter: Fix for boolean arrays
Uses bare filename to pass to `dlopen` when the full path cannot be detected. This helps on systems where library paths are not the same as $PATH.
Dereference pointers when generating getters for pointer variables. Otherwise, the managed instance would point to the pointer itself rather than the object at the native instance's address.
…ono#1765) * Fix missing Attribute dtor in GCC 11. Parser bindings are expecting this, yet this was optimized out under GCC 11. * Improve error handling for failed library parsing. * Make the converted declaration cache more robust. We were getting a failure due to duplicated original pointers. Make it take the declaration kind into account as a key to the cache. * Change ConsoleDriver.Run to return a failure bool.
* support clang 15.0.7 * Fix Premake archive logic to work with official releases. * Try and upgrade CI to latest OS versions. * Try and fix LLD link call in parser. * CI fixes. * Enable VS 2019 and VS 2022 for LLVM windows workflow. * Update to a more recent LLVM revision. * More build fixes. * Use the system linker for linking symbols libraries outside Windows. Builtin lld is giving some weird linking errors when linking with the new LLVM version. We probably need to set some custom options. Using the system linker should be a better idea anyway, more robust and future proof. --------- Co-authored-by: you74674 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously I grafted individual changes over, so this PR appears to bring in more changes than it actually does.