Builder ffmpeg-solaris10-i386 Build #13464

Results:

Failed shell_2 shell_3 shell_4 shell_5

SourceStamp:

BuildSlave:

Reason:

The SingleBranchScheduler scheduler named 'schedule-ffmpeg-solaris10-i386' triggered this build

Steps and Logfiles:

1. git update ( 5 secs )
   1. stdio
2. shell 'gsed -i ...' ( 0 secs )
   1. stdio
3. shell_1 'gsed -i ...' ( 0 secs )
   1. stdio
4. shell_2 'gsed -i ...' failed ( 0 secs )
   1. stdio
5. shell_3 './configure --samples="../../../ffmpeg/fate-suite" ...' failed ( 7 secs )
   1. stdio
   2. config.log
6. shell_4 'gmake fate-rsync' failed ( 0 secs )
   1. stdio
7. shell_5 '../../../ffmpeg/fate.sh ../../../ffmpeg/fate_config.sh' failed ( 2 secs )
   1. stdio
   2. configure.log
   3. compile.log
   4. test.log

Build Properties:

Forced Build Properties:

Responsible Users:

1. Guangyu Sun

   sunguangyucnohnoyoudont@gmail.com
2. Martin Storsjö

   martinohnoyoudont@martin.st

Timing:

All Changes:

:

1. Change #261360

   Category	ffmpeg
   Changed by	Martin Storsjö <martinohnoyoudont@martin.st>
   Changed at	Tue 17 Mar 2026 21:37:53
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	1f7ed8a78de1da743a359913ce05cc258a400b5d

   Comments

   aarch64: hevcdsp: Make returns match the call site
   For cases when returning early without updating any pixels, we
   previously returned to return address in the caller's scope,
   bypassing one function entirely. While this may seem like a neat
   optimization, it makes the return stack predictor mispredict
   the returns - which potentially can cost more performance than
   it gains.
   
   Secondly, if the armv9.3 feature GCS (Guarded Control Stack) is
   enabled, then returns _must_ match the expected value; this feature
   is being enabled across linux distributions, and by fixing the
   hevc assembly, we can enable the security feature on ffmpeg as well.

   Changed files

   • libavcodec/aarch64/hevcdsp_deblock_neon.S

2. Change #261361

   Category	ffmpeg
   Changed by	Martin Storsjö <martinohnoyoudont@martin.st>
   Changed at	Tue 17 Mar 2026 21:37:53
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	846746be4b8edd66be8be2c123b0072de2636e9d

   Comments

   aarch64: Add Armv9.3-A GCS (Guarded Control Stack) support
   Signal that our assembly is compliant with the GCS feature, if
   the GCS feature is enabled in the compiler (available since Clang
   18 and GCC 15) - this is enabled by -mbranch-protection=standard
   with a new enough compiler.
   
   GCS doesn't require any specific modifications to the assembly
   code, but requires that all functions return to the expected call
   address (checked through a shadow stack).

   Changed files

   • libavutil/aarch64/asm.S

3. Change #261362

   Category	ffmpeg
   Changed by	Guangyu Sun <sunguangyucnohnoyoudont@gmail.com>
   Changed at	Tue 17 Mar 2026 21:39:59
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	34bff02984180fa42af3406cbe09d4c5820715c1

   Comments

   avcodec/libvpxenc: fix sRGB colorspace for non-RGB pixel formats
   When encoding VP9 with a YUV pixel format (e.g. yuv420p) and
   AVCOL_SPC_RGB colorspace metadata, libvpxenc unconditionally set
   VPX_CS_SRGB. This produced a spec-violating bitstream: Profile 0
   (4:2:0) with sRGB colorspace, which is only valid for Profile 1/3
   (4:4:4). The resulting file is undecodable.
   
   Fix this by setting ctx->vpx_cs to VPX_CS_SRGB in set_pix_fmt()
   for 4:4:4 YUV formats when AVCOL_SPC_RGB is set, matching the
   existing GBRP path. This covers the legitimate case of RGB data in
   YUV444 containers (e.g. H.264 High 4:4:4 with identity matrix).
   
   With this change, any AVCOL_SPC_RGB that reaches the switch in
   set_colorspace() is guaranteed to be a subsampled format where
   sRGB is invalid. Return an error so the user can fix their
   pipeline rather than silently producing incorrect output.
   
   To reproduce:
   
     ffmpeg -f lavfi -i testsrc=s=64x64:d=1:r=1 \
       -c:v libvpx-vp9 -pix_fmt yuv420p -colorspace rgb bad.webm
     ffprobe bad.webm
     # -> "vp9 (Profile 0), none(pc, gbr/...), 64x64"
     ffmpeg -i bad.webm -f null -
     # -> 0 frames decoded, error
   
   See also:
     https://issues.webmproject.org/487307225
   
   Signed-off-by: Guangyu Sun <gsun@roblox.com>
   Signed-off-by: James Zern <jzern@google.com>

   Changed files

   • libavcodec/libvpxenc.c
   • libavcodec/version.h