1. 15 Mar, 2018 3 commits
  2. 13 Mar, 2018 1 commit
  3. 07 Mar, 2018 2 commits
  4. 05 Mar, 2018 1 commit
  5. 02 Mar, 2018 1 commit
  6. 01 Mar, 2018 3 commits
  7. 27 Feb, 2018 1 commit
    • Aleix Pol Gonzalez's avatar
      Make sure we don't crash when stopping all jobs · 8430d305
      Aleix Pol Gonzalez authored
      Summary:
      If we don't emit result, the ExecuteCompositeJob doesn't relise that
      it's failing and keeps the dangling object. Calling stop all processes
      would result in a crash then.
      
      Test Plan:
      * run app
      * run app again
      * choose to kill the first instance
      * stop all processes
      
      Reviewers: #kdevelop, mwolff
      
      Reviewed By: #kdevelop, mwolff
      
      Subscribers: mwolff, kdevelop-devel
      
      Differential Revision: https://phabricator.kde.org/D10874
      8430d305
  8. 25 Feb, 2018 1 commit
  9. 22 Feb, 2018 1 commit
    • Friedrich W. H. Kossebau's avatar
      Help automoc to find metadata JSON files referenced in the code · d4378dc3
      Friedrich W. H. Kossebau authored
      Summary:
      automoc by itself can only detect metadata files referenced by direct
      usage of the Q_PLUGIN_METADATA macro. It does not do any C++ preprocessor
      evaluation. Instead it needs to be helped with regexp-based filter rules for
      detecting any names of files used as additional moc input.
      See docs for AUTOMOC_DEPEND_FILTERS for further details.
      
      Test Plan:
      Changing a JSON file and running make results in the related *.moc file being
      regenerated and the related object file being recompiled.
      qtplugininfo shows that the created plugin binary has up-to-date JSON content.
      
      Reviewers: #kdevelop, apol, kfunk
      
      Reviewed By: #kdevelop, apol
      
      Subscribers: kdevelop-devel
      
      Differential Revision: https://phabricator.kde.org/D10693
      d4378dc3
  10. 20 Feb, 2018 1 commit
  11. 19 Feb, 2018 1 commit
  12. 18 Feb, 2018 1 commit
  13. 15 Feb, 2018 1 commit
  14. 13 Feb, 2018 1 commit
  15. 06 Feb, 2018 1 commit
  16. 05 Feb, 2018 1 commit
  17. 02 Feb, 2018 1 commit
  18. 18 Jan, 2018 3 commits
  19. 17 Jan, 2018 2 commits
  20. 16 Jan, 2018 7 commits
  21. 15 Jan, 2018 3 commits
  22. 10 Jan, 2018 3 commits
    • Milian Wolff's avatar
      Performance: Reuse the global icon loader · 94ed49ac
      Milian Wolff authored
      Summary:
      I just found a noticeable GUI hang when showing a problem widget
      for a missing include path. There, the profiler pointed me at
      KIconLoader which was reconstructed whenever we query for the icon
      representing the severity of a problem.
      
      By reusing the global icon loader, we can get the information from
      the cache which is significantly faster.
      
      Reviewers: #kdevelop
      
      Subscribers: kdevelop-devel
      
      Differential Revision: https://phabricator.kde.org/D9783
      94ed49ac
    • Milian Wolff's avatar
      Cache ProblemPointers per translation unit · f2a6941e
      Milian Wolff authored
      Summary:
      For visibility purposes, all 'inclue file not found' errors are
      associated with all files in a TU, since these usually completely
      break the interpretation of a file. But in some situations, this
      triggers a severe performance degradation:
      
      When the TU has a deep include stack depth and a file is not found
      somewhere at the bottom of the stack, then it will have one child
      diagnostic for every "included from ..." file higher up in the stack.
      Now if we would repeatedly build and intern the KDevelop::Problem
      representation for these diagnostics, for every file in the TU, we
      sometimes ended up spending *minutes* to create all the problems
      in ParseSession::problemsForFile!
      
      To workaround this situation, cache the ProblemPointer in the
      ParseSessionData for a given translation unit. This way, we will
      only convert a given diagnostic and its child diagnostics once per TU
      instead of once per file contained in a TU.
      
      In my case this brings down the time spent in problemsForFile for a
      single TU from ~7min (sic!) down to ~12s. While the latter is still
      a lot, this is already much more bearable.
      
      BUG: 386720
      
      Reviewers: #kdevelop
      
      Subscribers: kdevelop-devel
      
      Differential Revision: https://phabricator.kde.org/D9772
      f2a6941e
    • Laurent Montel's avatar
      Remove unused file · 3881efbd
      Laurent Montel authored
      (cherry picked from commit d212fa1d)
      3881efbd