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

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

    XMLWordPrintable

Details

    Description

      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?

      Attachments

        Activity

          drulli Ulli Hafner added a comment -

          Yes, that should be possible.

          Since I don't use gcc by myself: are you interested in updating the parser and testcases? It shouldn't be very complicated to change the current behavior.

          drulli Ulli Hafner added a comment - Yes, that should be possible. Since I don't use gcc by myself: are you interested in updating the parser and testcases? It shouldn't be very complicated to change the current behavior.

          Updating the actual code is logistically/legally challenging. I could probably create and provide regex / jelly script / example / from warnings parser that shows the matching concepts if that helps.

          moncreaff Greg Moncreaff added a comment - Updating the actual code is logistically/legally challenging. I could probably create and provide regex / jelly script / example / from warnings parser that shows the matching concepts if that helps.
          drulli Ulli Hafner added a comment -

          Since I don't use GCC I can't do much here. Please reopen if you have a patch or test case to improve the output of the parser.

          drulli Ulli Hafner added a comment - Since I don't use GCC I can't do much here. Please reopen if you have a patch or test case to improve the output of the parser.

          I've implemented classification of warnings produced by gcc 4.6 or later.
          https://github.com/yoichi/warnings-plugin/commit/04da9970e546183c1c1d3e204c7b8254525de241

          yoichi Yoichi Nakayama added a comment - I've implemented classification of warnings produced by gcc 4.6 or later. https://github.com/yoichi/warnings-plugin/commit/04da9970e546183c1c1d3e204c7b8254525de241
          drulli Ulli Hafner added a comment -

          Thanks for adding! Can you please create a pull request? Then it would be easier to merge...

          drulli Ulli Hafner added a comment - Thanks for adding! Can you please create a pull request? Then it would be easier to merge...

          Code changed in jenkins
          User: Yoichi NAKAYAMA
          Path:
          src/main/java/hudson/plugins/warnings/parser/Gcc4CompilerParser.java
          src/test/java/hudson/plugins/warnings/parser/Gcc4CompilerParserTest.java
          src/test/resources/hudson/plugins/warnings/parser/issue11799.txt
          http://jenkins-ci.org/commit/warnings-plugin/04da9970e546183c1c1d3e204c7b8254525de241
          Log:
          JENKINS-11799 Classify warnings by gcc 4.6 or later.

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Yoichi NAKAYAMA Path: src/main/java/hudson/plugins/warnings/parser/Gcc4CompilerParser.java src/test/java/hudson/plugins/warnings/parser/Gcc4CompilerParserTest.java src/test/resources/hudson/plugins/warnings/parser/issue11799.txt http://jenkins-ci.org/commit/warnings-plugin/04da9970e546183c1c1d3e204c7b8254525de241 Log: JENKINS-11799 Classify warnings by gcc 4.6 or later.

          Code changed in jenkins
          User: johnou
          Path:
          src/main/java/hudson/plugins/warnings/parser/Gcc4CompilerParser.java
          src/test/java/hudson/plugins/warnings/parser/DynamicParserTest.java
          http://jenkins-ci.org/commit/warnings-plugin/b137e727fc6fb4ecfe6a381e7d514bc4cdf1627d
          Log:
          [FIXED JENKINS-11799] improve warning category for gcc 4.6 or later.

          Compare: https://github.com/jenkinsci/warnings-plugin/compare/2d43fdf6f0fb...b137e727fc6f

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: johnou Path: src/main/java/hudson/plugins/warnings/parser/Gcc4CompilerParser.java src/test/java/hudson/plugins/warnings/parser/DynamicParserTest.java http://jenkins-ci.org/commit/warnings-plugin/b137e727fc6fb4ecfe6a381e7d514bc4cdf1627d Log: [FIXED JENKINS-11799] improve warning category for gcc 4.6 or later. Compare: https://github.com/jenkinsci/warnings-plugin/compare/2d43fdf6f0fb...b137e727fc6f

          johnu,
          Thank you for correcting the code.
          I found 4.19 is released, but Changelog is not written in https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin yet.

          yoichi Yoichi Nakayama added a comment - johnu, Thank you for correcting the code. I found 4.19 is released, but Changelog is not written in https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin yet.
          drulli Ulli Hafner added a comment -

          Feel free to add the change log entry, I did not make the merge and the release...

          drulli Ulli Hafner added a comment - Feel free to add the change log entry, I did not make the merge and the release...

          People

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

            Dates

              Created:
              Updated:
              Resolved: