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
Load (and others (like GEP) supporting the new opaue pointer concept with back-compat for typed pointers are incorrectly using the pointer type as the type pointer, however, it turns out, they should acully use the pointee type.
The text was updated successfully, but these errors were encountered:
- Deprecated InstructionBuilder.Load() single arg form, in favor of overload that accepts a type param for opaque pointers.
- Updated Analyzers to latest version and cleaned up code to correspond with changes in rules.
- Updated ANTLR4 version for Kaleidoscope Grammar.
- Added additional array marshaling info to the bindings generator to account for In arrays on some missed APIs
- Added ElementType to Alloca Instruction to provide a simple property to get the allocated type.
- Fixed GEP arg checks to validate args and indexes for arbitrary depth.
- Added SkipDocs switch to BuildAll.ps1 to allow faster inner loop development when doc builds aren't relevant.
* Fixes#84,#85,#86
- Deprecated InstructionBuilder.Load() single arg form, in favor of overload that accepts a type param for opaque pointers.
- Updated Analyzers to latest version and cleaned up code to correspond with changes in rules.
- Updated ANTLR4 version for Kaleidoscope Grammar.
- Added additional array marshaling info to the bindings generator to account for In arrays on some missed APIs
- Added ElementType to Alloca Instruction to provide a simple property to get the allocated type.
- Fixed GEP arg checks to validate args and indexes for arbitrary depth.
- Added SkipDocs switch to BuildAll.ps1 to allow faster inner loop development when doc builds aren't relevant.
* Added additional arg checks to Context Construction
Load (and others (like GEP) supporting the new opaue pointer concept with back-compat for typed pointers are incorrectly using the pointer type as the type pointer, however, it turns out, they should acully use the pointee type.
The text was updated successfully, but these errors were encountered: