Builder ffmpeg-solaris10-sparc Build #12372

Results:

Failed shell_2 shell_3 shell_4 shell_5

SourceStamp:

BuildSlave:

Reason:

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

Steps and Logfiles:

1. git update ( 20 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 ( 2 mins, 40 secs )
   1. stdio
   2. config.log
6. shell_4 'gmake fate-rsync' failed ( 3 secs )
   1. stdio
7. shell_5 '../../../ffmpeg/fate.sh ../../../ffmpeg/fate_config.sh' failed ( 5 secs )
   1. stdio
   2. configure.log
   3. compile.log
   4. test.log

Build Properties:

Forced Build Properties:

Responsible Users:

1. Jiawei

   jiaweiohnoyoudont@iscas.ac.cn

Timing:

All Changes:

:

1. Change #242225

   Category	ffmpeg
   Changed by	Jiawei <jiaweiohnoyoudont@iscas.ac.cn>
   Changed at	Wed 06 Aug 2025 10:05:05
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	1464930696f593320352a6f928fad6f50ade8f8b

   Comments

   configure: don't disable '-ftree-vectorize' on GCC >= 13 on major architectures
   This changes configure to stop disabling -ftree-vectorize on
   GCC versions 13 and newer, on major architectures.
   
   Background:
   - Original `-fno-tree-vectorize` was added in 2009 in commit
     973859f5230e to avoid compiler errors.
   - Re-enabled in 2016 in commit cb8646af24bd but caused failures due
     to inline CABAC assembly issues and was disabled again in
     fd6dbc53855fb.
   - Commit 182663a58a7a in 2023 fixed the inline CABAC assembly issues.
   - Recent versions of GCC, in particular 13 and newer, seem to
     generally work reliably with respect to vectorization, although bugs
     have been observed on Loongarch.
   
   Cautiously allow the GCC default of having vectorization enabled,
   on major architectures where we expect to see enough testing. If
   further issues are observed, they should be reported and noted here in
   configure, so the workarounds can be scoped and version limited.

   Changed files

   • Changelog
   • configure