Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-11799

GCC - better categories - Parser "GNU compiler (gcc)"




      It seems the categories are underutilized. (Just "GCC Error" and "GCC Warning"). Is it possible to have finer grain bins based on the actual warning text, stripping out warning instance variability?.

      E.g.(not sure if it is worth prefixing with "GCC Warning" or not)
      GCC Warning - unused variable
      GCC Warning - comparison is always false due to limited range of data type
      GCC Warning - incompatible implicit declaration of built-in function
      GCC Warning - defined but not used
      GCC Warning - implicit declaration of function
      GCC Warning - may be used uninitialized in this function
      GCC Warning - return type of 'main' is not 'int'
      GCC Warning - return type defaults to 'int'
      GCC Warning - format expects type
      GCC Warning - pointer targets in differ in signedness

      and for anything that didn't match something more specific:

      GCC Warning - other

      This would allow better summarization of issues in assessing state of the code.

      This stratagem may apply to all GCC versions of compilers?



          moncreaff Greg Moncreaff created issue -
          drulli Ulli Hafner made changes -
          Field Original Value New Value
          Priority Major [ 3 ] Minor [ 4 ]
          drulli Ulli Hafner made changes -
          Resolution Won't Fix [ 2 ]
          Status Open [ 1 ] Resolved [ 5 ]
          yoichi Yoichi Nakayama made changes -
          Resolution Won't Fix [ 2 ]
          Status Resolved [ 5 ] Reopened [ 4 ]
          scm_issue_link SCM/JIRA link daemon made changes -
          Resolution Fixed [ 1 ]
          Status Reopened [ 4 ] Resolved [ 5 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 142042 ] JNJira + In-Review [ 189951 ]


            drulli Ulli Hafner
            moncreaff Greg Moncreaff
            0 Vote for this issue
            3 Start watching this issue