1. 27 May, 2020 1 commit
  2. 22 Mar, 2017 1 commit
    • Martin Storsjö's avatar
      libavutil: Hook up the rest of the gcc specific attributes to clang as well · 8e234615
      Martin Storsjö authored
      Hook up all attributes that don't have a MSVC specific version at the
      moment.
      
      See f637046d for details.
      
      These don't seem to be critical for building with clang in MSVC mode
      though, and thus haven't been hooked up until now.
      
      These seem to build fine with as old clang as 3.3 at least.
      (clang 3.3 disguises itself as gcc 4.2 normally, so all of these
      have been used for clang before, except for av_cold.)
      
      The clang version numbers themselves are useless for detecting what
      attributes are available, since Apple's clang builds use a completely
      different versioning (presenting itself as e.g. clang 8.0 instead
      of 3.8).
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      8e234615
  3. 21 Mar, 2017 1 commit
  4. 21 Jul, 2016 1 commit
    • Martin Storsjö's avatar
      libavutil: Always use some GCC style attributes on clang · f637046d
      Martin Storsjö authored
      Clang normally disguises as GCC (defining __GNUC__), and thus get
      all the normal GCC specific attributes.
      
      Clang can also work as a drop-in replacement for MSVC, and in these
      cases, it doesn't define __GNUC__, but defines _MSC_VER instead.
      
      Even in these setups, it still supports the GCC style attributes,
      thus use them, especially where there isn't any MSVC specific
      version, or where the MSVC specific version doesn't work on clang
      (for DECLARE_ASM_CONST).
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      f637046d
  5. 05 Oct, 2015 1 commit
    • Ganesh Ajjanagadde's avatar
      avutil/attributes: add av_warn_unused_result · 1d4af04a
      Ganesh Ajjanagadde authored
      GCC 3.4 introduced an attribute warn_unused_result to warn when a programmer
      discards the return value. Applying this judiciously across the codebase can help
      in fixing a lot of problems. At a high level, functions which return error codes
      should always be checked. More concretely, consider the functions ff_add_format
      and the like in avfilter/formats.h. A quick examination shows that a large portion
      of libavfilter fails to handle the associated errors, usually AVERROR(ENOMEM).
      The above example was where I observed the utility of this, but it should be
      useful in many places across the code base.
      Signed-off-by: 's avatarGanesh Ajjanagadde <gajjanagadde@gmail.com>
      Signed-off-by: 's avatarMichael Niedermayer <michael@niedermayer.cc>
      1d4af04a
  6. 18 Sep, 2015 1 commit
  7. 16 Feb, 2015 1 commit
  8. 03 Nov, 2013 1 commit
  9. 21 Sep, 2013 1 commit
  10. 20 Sep, 2013 2 commits
  11. 06 Sep, 2013 1 commit
  12. 16 Jul, 2012 1 commit
  13. 03 Jul, 2012 2 commits
  14. 30 Jun, 2012 1 commit
  15. 17 Jun, 2012 2 commits
  16. 15 Jun, 2012 2 commits
  17. 11 Nov, 2011 1 commit
  18. 25 Sep, 2011 1 commit
  19. 23 Jun, 2011 1 commit
  20. 23 Mar, 2011 1 commit
  21. 19 Mar, 2011 1 commit
  22. 02 Mar, 2011 1 commit
  23. 31 Jan, 2011 2 commits
  24. 10 Nov, 2010 1 commit
  25. 13 May, 2010 1 commit
  26. 20 Apr, 2010 1 commit
  27. 02 Apr, 2010 1 commit
  28. 08 Mar, 2010 1 commit