Align in-memory splice-junction records#2699
Open
justinblethrow-cloud wants to merge 1 commit into
Open
Conversation
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.
Summary
Junctionrecord.vector<uint64>to guarantee suitable base alignment.Problem
The current 23-byte record places 32-bit counters at offsets 11 and 15 and 16-bit overhangs at offsets 19 and 21.
Junctionthen exposes typed pointers to those fields and dereferences them. UBSan reports these stores during normal spliced-read mapping, beginning inReadAlign_outputTranscriptSJ.cpp.This is an internal runtime buffer change only; no genome-index or output-file format changes.
Validation
extras/tests/scripts/testJunctionAlignment.shpasses; its static assertions fail against unmodified 2.7.11b on the storage type, field offsets, and record stride.SJ.out.tab, andReadsPerGene.out.tabare byte-identical to unmodified 2.7.11b.