-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[io] Add support for long range references in TBufferFile.cxx #21193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
pcanal
wants to merge
22
commits into
root-project:master
from
pcanal:Arlesienne_LongRangeReferences
Closed
[io] Add support for long range references in TBufferFile.cxx #21193
pcanal
wants to merge
22
commits into
root-project:master
from
pcanal:Arlesienne_LongRangeReferences
+1,028
−429
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
Member
pcanal
commented
Feb 8, 2026
Fixes root-project#14770 [io] add more checks in TBuffer functions as suggested by jblomer
In order to support 64 bits byte counts, which do not fit in the space reserved for them in the stream (4 bytes minus 2 control bits) and to work around the fact that the variables that holds the position and the byte count information in Streamer functions are only 32 bits (see arguments to TBufferFile::WriteVersion and TBufferFile::ReadVersion), we need to pass them indirectly when they needs 64 bits Since the streaming is inherently serial, we can leverage the sequence of calls and cache the 64 bits values in a queue. The bytecount that can not be stored in place inside the io stream will be held in a collection (fByteCounts) that need to be stored externally to the buffer.
Note to store and restore the larger than 1GB byte count use:
// Copy the content of the const reference.
auto bytecounts{b.GetByteCounts()};
...
b.SetByteCounts(std::move(bytecounts));
For now, the testing of the long range references is disabled.
References for class names and objects are stored in 64bits whenever they are located past 1GB. This is the 'only' option as there are no control bits left to distinguish between a 32bits and a 64bits reference.
Reference in the longRange section (>1GB) are now tagged so that we can differentiate nullptr (stored as only 32 bits) from short reference stored in the longRange section (i.e. those are stored in 64 bits but have only zeros in the high bit).
Member
Author
|
Wrong target branch. |
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.