1. 30 Nov, 2015 1 commit
    • Ganesh Ajjanagadde's avatar
      avcodec/ac3: always use hardcoded tables · 7b11eead
      Ganesh Ajjanagadde authored
      The table in question is a 253 byte one. In fact, it turns out that
      dynamic generation of the table results in an increased binary size.
      
      Code compiled with GCC 5.2.0, x86-64 (size in bytes), before and after
      patch:
      old: 62321064 libavcodec/libavcodec.so.57
      new: 62320536 libavcodec/libavcodec.so.57
      
      Thus, it always make sense to statically allocate this.
      
      Tested with FATE with/without --enable-hardcoded-tables.
      Reviewed-by: 's avatarwm4 <nfxjfg@googlemail.com>
      Signed-off-by: 's avatarGanesh Ajjanagadde <gajjanagadde@gmail.com>
      7b11eead
  2. 09 Jan, 2014 1 commit
  3. 18 Oct, 2012 1 commit
    • Martin Storsjö's avatar
      Add support for building shared libraries with MSVC · d66c52c2
      Martin Storsjö authored
      This requires the makedef perl script by Derek, from the
      c89-to-c99 repo. That scripts produces a .def file, listing
      the symbols to be exported, based on the gcc version scripts
      and the built object files.
      
      To properly load non-function symbols from DLL files, the
      data symbol declarations need to have the attribute
      __declspec(dllimport) when building the calling code. (On mingw,
      the linker can fix this up automatically, which is why it has not
      been an issue so far. If this attribute is omitted, linking
      actually succeeds, but reads from the table will not produce the
      desired results at runtime.)
      
      MSVC seems to manage to link DLLs (and run properly) even if
      this attribute is present while building the library itself
      (which normally isn't recommended) - other object files in the
      same library manage to link to the symbol (with a small warning
      at link time, like "warning LNK4049: locally defined symbol
      _avpriv_mpa_bitrate_tab imported" - it doesn't seem to be possible
      to squelch this warning), and the definition of the tables
      themselves produce a warning that can be squelched ("warning C4273:
      'avpriv_mpa_bitrate_tab' : inconsistent dll linkage, see previous
      definition of 'avpriv_mpa_bitrate_tab').
      
      In this setup, mingw isn't able to link object files that refer to
      data symbols with __declspec(dllimport) without those symbols
      actually being linked via a DLL (linking avcodec.dll ends up with
      errors like "undefined reference to `__imp__avpriv_mpa_freq_tab'").
      The dllimport declspec isn't needed at all in mingw, so we simply
      choose not to declare it for other compilers than MSVC that requires
      it. (If ICL support later requires it, the condition can be extended
      later to include both of them.)
      
      This also implies that code that is built to link to a certain
      library as a DLL can't link to the same library as a static library.
      Therefore, we only allow building either static or shared but not
      both at the same time. (That is, static libraries as such can be,
      and actually are, built - this is used for linking the test tools to
      internal symbols in the libraries - but e.g. libavformat built to
      link to libavcodec as a DLL cannot link statically to libavcodec.)
      
      Also, linking to DLLs is slightly different from linking to shared
      libraries on other platforms. DLLs use a thing called import
      libraries, which is basically a stub library allowing the linker
      to know which symbols exist in the DLL and what name the DLL will
      have at runtime.
      
      In mingw/gcc, the import library is usually named libfoo.dll.a,
      which goes next to a static library named libfoo.a. This allows
      gcc to pick the dynamic one, if available, from the normal -lfoo
      switches, just as it does for libfoo.a vs libfoo.so on Unix. On
      MSVC however, you need to literally specify the name of the import
      library instead of the static library.
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      d66c52c2
  4. 23 Feb, 2012 1 commit
  5. 24 May, 2011 1 commit
    • Justin Ruggles's avatar
      ac3enc: add channel coupling support · 7f3a7b5c
      Justin Ruggles authored
      Channel coupling is an optional AC-3 feature that increases quality by
      combining high frequency information from multiple channels into a
      single channel. The per-channel high frequency information is sent with
      less accuracy in both the frequency and time domains. This allows more
      bits to be used for lower frequencies while preserving enough
      information to reconstruct the high frequencies.
      7f3a7b5c
  6. 29 Mar, 2011 1 commit
  7. 19 Mar, 2011 1 commit
  8. 26 Jan, 2011 1 commit
  9. 25 Jan, 2011 1 commit
  10. 08 Jan, 2011 1 commit
  11. 14 Dec, 2010 1 commit
  12. 19 Apr, 2009 1 commit
  13. 17 Apr, 2009 2 commits
  14. 19 Jan, 2009 1 commit
  15. 31 Aug, 2008 1 commit
  16. 03 Aug, 2008 1 commit
  17. 09 May, 2008 1 commit
  18. 24 Apr, 2008 1 commit
  19. 09 Dec, 2007 1 commit
  20. 17 Oct, 2007 1 commit
  21. 25 Apr, 2007 2 commits
  22. 18 Mar, 2007 1 commit
  23. 11 Mar, 2007 1 commit
  24. 09 Mar, 2007 1 commit
  25. 07 Oct, 2006 1 commit
  26. 10 Sep, 2006 1 commit
  27. 03 Sep, 2006 1 commit
  28. 28 Apr, 2006 1 commit
  29. 22 Apr, 2006 1 commit
  30. 06 Mar, 2006 1 commit
  31. 17 Dec, 2005 1 commit
  32. 26 Jun, 2004 1 commit
  33. 06 Mar, 2003 1 commit
  34. 11 Feb, 2003 1 commit
  35. 28 Oct, 2002 1 commit
  36. 22 Jul, 2001 1 commit