This affects all kind of spaces (' ',^I,^M,^L,...): actually
[:space:] regex character set.
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@29306 b3059339-0415-0410-9bf9-f77b7e298cf2
Neither variant is valid C99 syntax, but __asm__ is the most portable variant.
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@27788 b3059339-0415-0410-9bf9-f77b7e298cf2
unlikely to make any difference. This reduces the diff to upstream.
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@27486 b3059339-0415-0410-9bf9-f77b7e298cf2
with __attribute__((always_inline)) declarations.
This fixes the build on Mac OS X 10.4.11.
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@27485 b3059339-0415-0410-9bf9-f77b7e298cf2
The original problem was that FSF and Apple gcc used a different syntax
for vector declarations, i.e. {} vs. (). Nowadays Apple gcc versions support
the standard {} syntax and versions that support {} are available on all
relevant Mac OS X versions. Thus the greater compatibility is no longer
worth cluttering the code with macros.
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@27350 b3059339-0415-0410-9bf9-f77b7e298cf2
set by configure instead of an OS-specific directive when #including altivec.h.
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@25356 b3059339-0415-0410-9bf9-f77b7e298cf2
The macro definition depends on compiler capabilities, not OS features.
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@25355 b3059339-0415-0410-9bf9-f77b7e298cf2
