Bring g1ConcurrentMark files up to current coding conventions

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Fixed
    • Priority: P4
    • 11
    • Affects Version/s: 9
    • Component/s: hotspot
    • gc
    • b10

      Look through the g1ConcurrentMark files and fix obvious coding style issues like:

       - camelCase variable and method naming
       - missing brackets around one-line if-statement bodies.
       - method naming (getters/setters)
       - use _g1h member variable instead of _g1 or another method local variable
       - use assert_at_safepoint* macros
       - remove incomprehensible comments

      and other stuff.

            Assignee:
            Thomas Schatzl
            Reporter:
            Thomas Schatzl
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: