Recherche avancée

Sur d’autres sites (2771)

• x86 : h264 : Don’t keep data in the redzone across function calls on 64 bit unix

  20 février 2012, par Martin Storsjö

  x86 : h264 : Don’t keep data in the redzone across function calls on 64 bit unix
  We know that the called function (ff_chroma_inter_body_mmxext)
  
  doesn’t touch the redzone, and thus will be kept intact - thus,
  
  this doesn’t fix any bug per se.
  However, valgrind’s memcheck tool intentionally assumes that the
  
  redzone is clobbered on every function call and function return
  
  (see a long comment in valgrind/memcheck/mc_main.c). This avoids
  
  false positives in that tool, at the cost of an extra stack pointer
  
  adjustment.
  The other alternative would be a valgrind suppression for this issue,
  
  but that’s an extra burden for everybody that wants to run libavcodec
  
  within valgrind.
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DH] libavcodec/x86/h264_deblock.asm

• avformat/internal : Hide BSF stuff only used by the core APIs

  10 mai 2022, par Andreas Rheinhardt

  avformat/internal : Hide BSF stuff only used by the core APIs
  The general demuxing API uses bitstream filters to extract extradata
  
  and the muxing API uses them in order to transform packets into
  
  the format desired by the target format. Therefore FFStream contains
  
  pointers to AVBSFContexts and lavf/internal.h includes lavc/bsf.h.
  Yet actually, only a few files files are supposed to use these,
  
  namely avformat.c, demux.c and mux.c. For all the other files,
  
  it should be an opaque type that they should not touch and that
  
  they need not know anything about. This can be achieved by not
  
  including these headers and using the structs instead of the
  
  corresponding typedefs.
  
  This also forces translation units that really use the BSF API
  
  themselves to include lavc/bsf.h directly instead of relying on
  
  indirect inclusions (a few other files also use the BSF API ;
  
  they already abided by this).
  
  Of course, it also avoids unnecessary rebuilds when bsf.h changes.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
  

  • [DH] libavformat/internal.h

• avcodec/sanm : better ANIMv1 engine support

  11 mars, par Manuel Lauss

  avcodec/sanm : better ANIMv1 engine support
   clear the front buffer with color 0 on the first FOBJ.
  
    Fixes a lot of Rebel Assault 1 videos and Rebel Assault 2 space
  
    scenes (e.g. 08PLAY.SAN which consists only of codec1/2/21 objects
  
    which only ever touch parts of the buffer).
  
   for ANIMv1 (Rebel Assault 1) : set palette index 0 to all zeroes.
  
    This fixes a lot of stray colors in e.g L1HANGAR.ANM, L2INTRO.ANM,
  
    space scenes.
  
   Esp in RA1, there are a lot of FRME objects which don't contain
  
    any video data (prebuffering some audio only). Account for that.
  
   In RA1 L2PLAY.ANM there are a few unaligned FOBJs, handle this
  
    in a generic way.
  Signed-off-by : Manuel Lauss <manuel.lauss@gmail.com>
  

  • [DH] libavcodec/sanm.c