Difference between revisions of "H.264 on CBE"

From esoterum.org
Jump to: navigation, search
(Compiling JM14.1 for CBE)
(Implementations)
Line 10: Line 10:
 
*Jonghan Park, Soonhoi Ha. [http://ieeexplore.ieee.org/iel5/4375779/4375780/04375797.pdf?isnumber=4375780&prod=CNF&arnumber=4375797&arSt=27&ared=32&arAuthor=Jonghan+Park%3B+Soonhoi+Ha  Performance Analysis of Parallel Execution of H.264 Encoder on the Cell Processor]. IEEE, ESTIMedia 2007.
 
*Jonghan Park, Soonhoi Ha. [http://ieeexplore.ieee.org/iel5/4375779/4375780/04375797.pdf?isnumber=4375780&prod=CNF&arnumber=4375797&arSt=27&ared=32&arAuthor=Jonghan+Park%3B+Soonhoi+Ha  Performance Analysis of Parallel Execution of H.264 Encoder on the Cell Processor]. IEEE, ESTIMedia 2007.
 
:-School of EECS, Seoul National University, Seoul, Korea
 
:-School of EECS, Seoul National University, Seoul, Korea
 +
*
 +
Hyunki Baik, Kue-Hwan Sihn, Yun-il Kim, Sehyun Bae, Najeong Han, and Hyo Jung Song. [http://www.ieeexplore.ieee.org/iel5/4455349/4457988/04458128.pdf?tp=&isnumber=4457988&arnumber=4458128 Analysis and Parallelization of H.264 decoder on Cell Broadband Engine Architecture]. Signal Processing and Information Technology. page(s): 791-795. 2007
 +
:-Samsung Electron. Co., Ltd., Suwon, Korea.
  
 
== Compiling JM14.1 for CBE ==
 
== Compiling JM14.1 for CBE ==
 
*Compiler requires switch <code>-fsigned-char</code> to set default signedness of <code>char</code> to signed.  This is an issue between x86 and PPC which use <code>signed</code> and <code>unsigned char</code> respectively, information on <code> signed char</code> here: [http://www.network-theory.co.uk/docs/gccintro/gccintro_71.html An Introduction to GCC]
 
*Compiler requires switch <code>-fsigned-char</code> to set default signedness of <code>char</code> to signed.  This is an issue between x86 and PPC which use <code>signed</code> and <code>unsigned char</code> respectively, information on <code> signed char</code> here: [http://www.network-theory.co.uk/docs/gccintro/gccintro_71.html An Introduction to GCC]
 
*Don't know yet if these flags from JM Makefile are needed: <code>-std=gnu99 -pedantic -ffloat-store -fno-strict-aliasing -m32</code>
 
*Don't know yet if these flags from JM Makefile are needed: <code>-std=gnu99 -pedantic -ffloat-store -fno-strict-aliasing -m32</code>

Revision as of 12:24, 8 August 2008

PS3

Login

  • ssh [user]@149.169.176.117

File Transfer

  • sftp [user]@149.169.176.117
  • put /home/mbaker/workspace/[project]/[file] [PS3 filename]
  • get [PS3 filename] /home/mbaker/workspace/[project]

Implementations

-School of EECS, Seoul National University, Seoul, Korea

Hyunki Baik, Kue-Hwan Sihn, Yun-il Kim, Sehyun Bae, Najeong Han, and Hyo Jung Song. Analysis and Parallelization of H.264 decoder on Cell Broadband Engine Architecture. Signal Processing and Information Technology. page(s): 791-795. 2007

-Samsung Electron. Co., Ltd., Suwon, Korea.

Compiling JM14.1 for CBE

  • Compiler requires switch -fsigned-char to set default signedness of char to signed. This is an issue between x86 and PPC which use signed and unsigned char respectively, information on signed char here: An Introduction to GCC
  • Don't know yet if these flags from JM Makefile are needed: -std=gnu99 -pedantic -ffloat-store -fno-strict-aliasing -m32