Remove compiler ras address masking - #7549
Merged
Merged
Conversation
Contributor
Author
|
@JBKingdon @klangman : FYI for any opinions you might have |
Contributor
Author
|
@dsouzai : would you mind reviewing please? |
Contributor
|
Sounds good to me. |
dsouzai
reviewed
Nov 18, 2024
dsouzai
left a comment
Contributor
There was a problem hiding this comment.
Overall LGTM aside from a couple of comments.
0xdaryl
force-pushed
the
maskaddresses
branch
from
November 18, 2024 21:40
336c867 to
28c5ba6
Compare
dsouzai
approved these changes
Nov 19, 2024
Contributor
|
jenkins build all |
Contributor
|
win build failure: I guess |
"Address masking" was an attempt to make compiler log files easier to compare by preventing addresses (that are likely to change between compilations) from being printed raw in a compilation log. It worked by intercepting the "printf" family of IO functions and checking whether any addresses were being printed with the `%p` format specifier, and instead of printing the address a "*Masked*" string was substituted instead. This feature was introduced at a time when text file comparison tools were not as robust as they are today. As well, these days, many addresses are output to the log without using `%p` making this feature less effective. Since it adds overhead and complexity to the logging path, has incomplete coverage, and is not widely used (if at all), remove it from the code base. Signed-off-by: Daryl Maier <maier@ca.ibm.com>
The passed in va_list is not used so it can be simply passed along. Also, remove unused `buffer` array. Signed-off-by: Daryl Maier <maier@ca.ibm.com>
0xdaryl
force-pushed
the
maskaddresses
branch
from
November 19, 2024 16:42
28c5ba6 to
a39eaca
Compare
Contributor
Author
|
Jenkins build all |
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.
"Address masking" was an attempt to make compiler log files easier to compare by preventing addresses (that are likely to change between compilations) from being printed raw in a compilation log. It worked by intercepting the "printf" family of IO functions and checking whether any addresses were being printed with the
%pformat specifier, and instead of printing the address a "Masked Address" string was substituted instead.This feature was introduced at a time when text file comparison tools were not as robust as they are today and many addresses are output to the log without using
%pmaking this feature less effective. Since it adds overhead and complexity to the logging path, has incomplete coverage, and is not widely used (if at all), remove it from the code base.Removing address masking was discussed briefly at the Oct 24 OMR Architecture Meeting with agreement to remove it.