Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
TR_X86ProcessorInfo is currently used in OMR because the compiler does not yet have access to the portlib. Therefore, it has to determine the processor features itself. In order to not initialize TR_X86ProcessorInfo multiple times a flag is set. However, it is a race possible if there are multiple compilations, as is the case in Eclipse OpenJ9. Because the processor feature flags were copied from the target TR::Environment set in TR::Compilation object, if two racing compilations had different target environments, the feature flags could become inconsistent. This commit initializes the processor info just once in OMR::CompilerEnv::initializeTargetEnvironment(). Signed-off-by: Irwin D'Souza <dsouzai.gh@gmail.com>
- Loading branch information
Showing
7 changed files
with
39 additions
and
50 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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