Repository navigation
Sync TileOP API with PTO 0.58.7 development golden - #279
Merged
Merged
Conversation
This was referenced Oct 17, 2026
Merged
zhoubot
marked this pull request as ready for review
October 17, 2026 11:10
zhoubot
enabled auto-merge (squash)
October 17, 2026 11:10
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
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.
PTO-SPEC development commit
f0a876e449a95d26841c5ee7affb4c905ebc5f5bis the golden source for the current 0.58.7 candidate. TileOP still carried the published 118-operation snapshot, the historical 0.58.3 engine projection, implicit last-use binders, and legacy TLSU/CUBE start spellings.This change pins the exact LinxISA
f77a8960f61f97c264a90b7aee757f99891b0943and PTO development golden identities, imports the 119-operation catalog, and regenerates the 32 VEC / 47 SFU / 28 TLSU / 12 CUBE projection. It marksTLEAas having no wrapper; the other 118 operation names are source-referenced, which is inventory evidence rather than semantic-completeness evidence.All source-bearing
B.IOT/B.IOSemissions in the jcore and region inline-assembly headers now use explicit.reuse, preserving existing source payloads under the golden rule that omission means last-use. TLSU/CUBE wrappers use canonicalBSTART.<operation> <dtype>syntax. The associatedTCONCAT_ASSandTTRANS_ASSpaths now reject instead of emitting retired raw selectors 96 and 110, and retired-operation pages no longer advertise executable bundles.Validation:
make check— passf77a8960...and PTOf0a876e...— passverify_pto0583_asm.shwith the companion LLVM PR docs: align range modifiers with pto-spec semantics #126 candidate — pass, including retained one-source/two-source/Shared binders, disassembly, invalid forms, and all 40 named TLSU/CUBE startsedb65a7681de90874d0c1fe4e6098f9e55ff8a00— 119/119 pass inllvm-mc, linx32 Clang IAS, and linx64 Clang IASThe target C++ object gate was not run locally because no Linx musl C++ sysroot is installed. The existing hosted required gate resolves LLVM branch
dev-llvm15_56, whereas companion LLVM PR #126 targetsmain. Its result therefore cannot establish target C++ object compatibility with the exactedb65a7candidate used in the local MC/IAS checks. That exact-candidate sysroot-backed C++ lane remains unverified and is a promotion dependency.