Re: PR31264 on 4.2.0 branch

["Richard Guenther" <richard dot guenther at gmail dot com>]

On 5/8/07, Ismail Dönmez <ismail@pardus.org.tr> wrote:
> Hi,
>
> Fix for PR31264 doesn't seem to be checked into 4.2.0 branch which breaks
> MPlayer SVN compilation with :
>
> cc -I../libavcodec -I../libavformat -Wdeclaration-after-statement -I. -I.. -I../libavutil -O4 -march=pentium-m -mtune=pentium-m -pipe
> -ffast-math -fomit-frame-pointer -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -I/usr/include -I/usr/include/  -I/usr/include/SDL  -D_REENTRANT  -I/usr/include/freetype2 -I/usr/include   -c -o
> demux_vqf.o demux_vqf.c
> demux_vqf.c: In function 'demux_open_vqf':
> demux_vqf.c:24: internal compiler error: in build_int_cst_wide, at tree.c:864
>
> [/packages/mplayer]> cc -v
> Using built-in specs.
> Target: i686-pc-linux-gnu
> Configured
> with: /var/pisi/gcc-4.2.0-23/work/gcc-4.2.0-20070430/configure --prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc/4.2.0
> --includedir=/usr/lib/gcc/i686-pc-linux-gnu/4.2.0/include --datadir=/usr/share/gcc/i686-pc-linux-gnu/4.2.0 --mandir=/usr/share/gcc/i686-pc-linux-gnu/4.2.0/man
> --infodir=/usr/share/gcc/i686-pc-linux-gnu/4.2.0/info --with-gxx-include-dir=/usr/lib/gcc/i686-pc-linux-gnu/4.2.0/include/g++-v3 --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu
> --disable-libgcj --disable-libssp --disable-multilib --disable-nls --disable-werror --enable-clocale=gnu --enable-__cxa_atexit --enable-languages=c,c++,objc,fortran --enable-libstdcxx-allocator=new --enable-shared
>  --enable-ssp --enable-threads=posix --enable-version-specific-runtime-libs --without-included-gettext --without-system-libunwind --with-system-zlib
> Thread model: posix
> gcc version 4.2.0 20070430 (prerelease) (Pardus Linux)
>
> It seems to be a one liner fix which is in mainline for some time, would it be
> ok to check it into 4.2.0 branch too?

Did you verify this is actually the same problem?  Note that this PR
isn't marked as
broken on 4.2.0 or as a regression, so you should probably file a new bugreport
against 4.2.0 and link to the old one.

Thanks,
Richard.