The C standard reserves identifiers starting with _ and a capital letter
for the system. Here is a patch that fixes a few instances in
libmpeg2/idct_mmx.c. As a positive side effect, the names of the
variables are much better than before.
I already committed this to the copy of idct_mmx.c in
Here is a patch to make some of the MMX optimizations available on
x86_64 as well. I have extracted it from the MPlayer local patch set.
Please apply.
Diego
Index: idct_mmx.c
===
--- idct_mmx.c (revision 1152)
+++ idct_mmx.c
Here is a patch to add consistent multiple inclusion guards to all
header files in libmpeg2. I have also used a LIBMPEG2_ prefix to avoid
possible namespace pollution issues. Please apply.
Diego
Index: include/mpeg2.h
===
---
Here is a trivial patch to remove a weirdness from all libmpeg2 license
headers: It says this program where it should really say mpeg2dec.
Diego
Index: include/mpeg2.h
===
--- include/mpeg2.h (revision 1162)
+++ include/mpeg2.h
Here is a patch to do away with all the outdated references to CVS and
give Subversion instructions instead.
Diego
Index: README
===
--- README (revision 1162)
+++ README (working copy)
@@ -155,33 +155,17 @@
could probably be
So, all patches that were posted recently have been applied. How about
making a libmpeg2 release now? A branch release would be very helpful
for me since it I could easily import it into MPlayer :)
Diego
-
This SF.net
Here is a patch to handle AltiVec vector declaration syntax in a
slightly better way. Yes, this reverts a patch I sent earlier :)
Apple's gcc accepts vector declarations with () instead of {} like the
FSF gcc. Newer variants of the Apple compiler understand {} as well and
complain about () when
On Fri, May 30, 2008 at 02:29:43PM +0200, Diego Biurrun wrote:
Here is a patch to handle AltiVec vector declaration syntax in a
slightly better way. Yes, this reverts a patch I sent earlier :)
Apple's gcc accepts vector declarations with () instead of {} like the
FSF gcc. Newer variants
On Thu, Oct 09, 2008 at 03:12:15PM +0200, Lionel Debroux wrote:
A nitpick about your patch that updates the FSF address: I noticed that
trunk/src/getopt.{c,h} remain untouched.
Yes, that was done on purpose, these files are from glibc, not libmpeg2.
What do people think ?
Your patch is
Here is a patch to make libmpeg2 headers compile standalone.
This allows #including them directly without worrying about
header inclusion order or having to #include system headers
before libmpeg2 headers.
Diego
Index: include/mpeg2.h
On Fri, Jun 11, 2010 at 11:56:09AM +0200, Sam Hocevar wrote:
On Thu, Jun 10, 2010, Diego Biurrun wrote:
Here is a patch to make libmpeg2 headers compile standalone.
This allows #including them directly without worrying about
header inclusion order or having to #include system headers
On Thu, Jun 24, 2010 at 10:41:22AM +0200, Diego Biurrun wrote:
On Sat, Jun 12, 2010 at 10:37:48AM +0200, Diego Biurrun wrote:
On Fri, Jun 11, 2010 at 11:56:09AM +0200, Sam Hocevar wrote:
On Thu, Jun 10, 2010, Diego Biurrun wrote:
Here is a patch to make libmpeg2 headers compile
I can reproduce a crash in libmpeg2 with MPlayer on the sample:
http://samples.mplayerhq.hu/MPEG2/libmpeg2-crash.vob
The crash happens both with the internal forked copy and with the
upstream version.
Here is a somewhat ugly patch that we used to apply to the forked
copy and that does fix the
The _fast integer types provide no realworld benefits, but may introduce
portability issues and are just plain ugly.
---
libmpeg2/idct_alpha.c | 14 +++---
1 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/libmpeg2/idct_alpha.c b/libmpeg2/idct_alpha.c
index 8e94219..490b659
On Mon, May 16, 2011 at 10:53:56PM +0300, Rémi Denis-Courmont wrote:
Le lundi 16 mai 2011 21:27:13 Diego Biurrun, vous avez écrit :
The _fast integer types provide no realworld benefits, but may introduce
portability issues and are just plain ugly.
int_fastXX_t are in ISO C just as intXX_t
On Tue, May 17, 2011 at 06:05:48PM +0300, Rémi Denis-Courmont wrote:
Le mardi 17 mai 2011 02:54:28 Diego Biurrun, vous avez écrit :
On Mon, May 16, 2011 at 10:53:56PM +0300, Rémi Denis-Courmont wrote:
Le lundi 16 mai 2011 21:27:13 Diego Biurrun, vous avez écrit :
The _fast integer types
Here is a small patch to move inline keywords to the front of function
declarations. This fixes some warnings with gcc and -Wextra where it
complains about the 'static' keyword not being at the beginning of a
function declaration. Apparently gcc gets tripped up and complains
about 'static'
17 matches
Mail list logo