1. 09 May, 2019 1 kayıt (commit)
  2. 03 May, 2019 1 kayıt (commit)
  3. 29 Nis, 2019 2 kayıt (commit)
  4. 09 Nis, 2019 1 kayıt (commit)
  5. 06 Mar, 2019 1 kayıt (commit)
  6. 05 Mar, 2019 1 kayıt (commit)
  7. 04 Mar, 2019 2 kayıt (commit)
  8. 01 Mar, 2019 1 kayıt (commit)
  9. 27 Şub, 2019 1 kayıt (commit)
  10. 09 Şub, 2019 1 kayıt (commit)
  11. 24 Ock, 2019 1 kayıt (commit)
  12. 21 Ock, 2019 1 kayıt (commit)
    • Stephan Bergmann's avatar
      Avoid -Werror=stringop-truncation · 26688cf0
      Stephan Bergmann yazdı
      ...as emitted by at least GCC 8.2 with --enable-optimized.  These are not
      actually problems, as in both cases strncpy(p,...,N-1) is used to copy a
      string into an area p of length N that has initially been zero-initialized, so
      p[N-1] will already contain NUL.  But add the (redundant) p[N-1]=NUL just in
      case, and to silence GCC (where the documentation explicitly recommends this
      additional write as a way to silence the warning).  Unfortunately, in hstyle.cxx
      at least GCC 8.2 with --enable-optimized would still emit the warning, even
      though it uses the recommended way of handling it, so needs to be silenced with
      a #pragma.
      
      Change-Id: Ie41f420c732c2bfb699903ebd21ce1a89dd2b236
      Reviewed-on: https://gerrit.libreoffice.org/66620
      Tested-by: Jenkins
      Reviewed-by: 's avatarStephan Bergmann <sbergman@redhat.com>
      26688cf0
  13. 28 Ara, 2018 1 kayıt (commit)
  14. 21 Ara, 2018 1 kayıt (commit)
  15. 19 Ara, 2018 1 kayıt (commit)
  16. 08 Ara, 2018 1 kayıt (commit)
  17. 25 Kas, 2018 1 kayıt (commit)
  18. 16 Kas, 2018 1 kayıt (commit)
  19. 10 Kas, 2018 1 kayıt (commit)
  20. 24 Eki, 2018 2 kayıt (commit)
  21. 23 Eki, 2018 1 kayıt (commit)
  22. 21 Eki, 2018 1 kayıt (commit)
  23. 19 Eki, 2018 3 kayıt (commit)
  24. 18 Eki, 2018 2 kayıt (commit)
  25. 09 Eki, 2018 1 kayıt (commit)
  26. 26 Eyl, 2018 1 kayıt (commit)
  27. 24 Eyl, 2018 1 kayıt (commit)
  28. 17 Eyl, 2018 1 kayıt (commit)
    • Stephan Bergmann's avatar
      New loplugin:external · 206b5b26
      Stephan Bergmann yazdı
      ...warning about (for now only) functions and variables with external linkage
      that likely don't need it.
      
      The problems with moving entities into unnamed namespacs and breaking ADL
      (as alluded to in comments in compilerplugins/clang/external.cxx) are
      illustrated by the fact that while
      
        struct S1 { int f() { return 0; } };
        int f(S1 s) { return s.f(); }
        namespace N {
          struct S2: S1 { int f() { return 1; } };
          int f(S2 s) { return s.f(); }
        }
        int main() { return f(N::S2()); }
      
      returns 1, both moving just the struct S2 into an nunnamed namespace,
      
        struct S1 { int f() { return 0; } };
        int f(S1 s) { return s.f(); }
        namespace N {
          namespace { struct S2: S1 { int f() { return 1; } }; }
          int f(S2 s) { return s.f(); }
        }
        int main() { return f(N::S2()); }
      
      as well as moving just the function f overload into an unnamed namespace,
      
        struct S1 { int f() { return 0; } };
        int f(S1 s) { return s.f(); }
        namespace N {
          struct S2: S1 { int f() { return 1; } };
          namespace { int f(S2 s) { return s.f(); } }
        }
        int main() { return f(N::S2()); }
      
      would each change the program to return 0 instead.
      
      Change-Id: I4d09f7ac5e8f9bcd6e6bde4712608444b642265c
      Reviewed-on: https://gerrit.libreoffice.org/60539
      Tested-by: Jenkins
      Reviewed-by: 's avatarStephan Bergmann <sbergman@redhat.com>
      206b5b26
  29. 10 Eyl, 2018 1 kayıt (commit)
  30. 09 Eyl, 2018 1 kayıt (commit)
  31. 08 Eyl, 2018 1 kayıt (commit)
  32. 07 Eyl, 2018 1 kayıt (commit)
  33. 21 Agu, 2018 1 kayıt (commit)
  34. 15 Agu, 2018 1 kayıt (commit)