Hi folks, I wanted to summarize the current status of the Solaris Studio FATE build as I know the output can sometimes be overwhelming, particularly with V=1 set. I've been focussing more of my time recently on assisting with gcc 4.7 on Solaris.
The following errors in the build are the most immediately apparent: 1. libavcodec/h264_cabac.c: it seems to be puking on the decode_significance* stuff in x86/h264_i386.h. It's currently conditionally compiled with an #if ARCH_X86 && HAVE_7REGS && !defined(BROKEN_RELOCATIONS), should it actually be ARCH_X86_32, or should this work equally well on 64-bit? 2. libavcodec/motion_est.c: not too sure on this one yet -- the compiler complains about "invalid instruction argument" in the generated assembly, I'm thinking it may have some correlation to the x86/mathops.h "impossible constraint" warnings peppered through the build logs. 3. libavcodec/x86/h264dsp_mmx.c: It is not fond of the h264_loop_filter_strength_iteration_mmx2() macro. A candidate for YASM? 4. libavcodec/x86/mlpdsp.c: This is for the assembly labels that are of type void. I sent a patch for this earlier this year, but M$(D+)(Bns suggested -- and I agree -- that this should probably be given the YASM treatment instead. 5. libavutil/x86/cpu.c: I also submitted a patch for this -- it seems suncc is not fond of our cpuid() macro. I'd appreciate any comments or suggestions on how to fix these. I am guessing that even when I have this building successfully that there will also still be some work to make FATE pass. We can tackle those later, unless people would rather I run FATE with the currently erroring modules disabled. Thanks in advance, Sean McG. _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
