JDK-8050482 : ReplacedNodes::dump() does not print to outputStream
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 9
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2014-07-15
  • Updated: 2023-07-21
  • Resolved: 2023-07-21
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.
JDK 9
9Resolved
Related Reports
Duplicate :  
Description
The implementation of ReplacedNodes::dump(outputStream *st) does not print to the outputStream st but dumps the output to tty. It is called by SafePointNode::dump_spec(..).

The IdealGraphPrinter uses dump_spec(..) to write to the graph file. If it encounters SafePointNodes the console output is flooded with messages.

To reproduce the bug use the following command line:
java -Xcomp -XX:PrintIdealGraphLevel=4 -XX:PrintIdealGraphFile="file.xml" -version

Output then looks like this:
[...]
replaced nodes: 26->176,176->192,197->220,220->237,249->250,250->264,269->287,287->304replaced nodes: 26->176,176->192,197->220,220->237,249->250,250->264,269->287,287->304replaced nodes: 26->176,176->192,197->220,220->237,249->250,250->264,269->287,287->304replaced nodes: 26->176,176->192,197->220,220->237,249->250,250->264,269->287,287->304replaced nodes: 26->176,176->192,197->220,220->237,249->250,250->264
[...]
Comments
Thanks for noticing, I should have checked.
15-07-2014

It's a duplicate of JDK-8048703
15-07-2014