JDK-8140405 : CompilerControl: Compiler.clear_directives doesn't clear the exclude state
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 9
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2015-10-23
  • Updated: 2023-10-09
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8149337 - compiler/compilercontrol/jcmd/PrintDirectivesTest.java fails
Relates :  
JDK-8137167 - JEP165: Compiler Control: Implementation task
Relates :  
JDK-8222103 - [testbug] compiler/compilercontrol/jcmd/ClearDirectivesFileStackTest may exceed VM limit
Sub Tasks
JDK-8140669 :  
Quarantine ClearDirectivesFileStackTest - Resolved
Description
Consider we have excluded some method with direcitve file. If this method have been sent to compilation, compilerBroker makes it be excluded from compilation forever. In compilerBroker::compilation_is_prohibited there is a just
    method->set_not_compilable(comp_level, !quietly, "excluded by CompileCommand");

If after that DCMD command Compiler.clear_directives have been invoked, the method would still be excluded from compilation.
Comments
It's unclear why ClearDirectivesFileStackTest is excluded based on this bug. My coleague Peter Januschke investigated this and figured the test is failing for a different reason. To our understanding it's a test setup problem. See also JDK-8222103.
08-04-2019
ILW = incorrect behavior; specific CompilerControl directives combination; none = MLH = P4
08-06-2016
RandomValidCommandsTest: -Djdk.test.lib.random.seed=7316599380790954951 "Could not add 35 more directives. Currently 19/50 directives." This should be the eror message.
13-03-2016
Summary: What’s broken is to make methods that where not compilable, compilable again when pushing a new directive or popping an old. This is new functionality and doesn't break anything old. Only the new tests can possibly be affected => P3
29-10-2015