On Wed, 2005-05-04 at 09:37, Anuradha Suraparaju wrote:
> I've attached a sample file to this email. The class defined in the cpp
> file is a cut down and modfied version of the class used in Dirac.
That is a fine bug report. You just need to put it in bugzilla if you
want us to do anything about
I've attached a sample file to this email. The class defined in the cpp
file is a cut down and modfied version of the class used in Dirac.
I compiled it using the following options:
g++ -mmmx -g -O3 test_mmx_diff4.cpp
The run time comparison is attached to this email as well.
Hope this helps.
Anuradha Suraparaju wrote:
My question is how do I report this as a bug? What information do I
need to provide in the bug report? Did anybody else face similar
problems with GCC-4.0.0 and MMX-enabled programs.
See
http://gcc.gnu.org/bugs.html
for info on reporting bugs.
If you can narrow this d
I used GCC-4.0.0 to build the Dirac project. I used the --enable-mmx
flag to enable MMX optimisations. Other versions of gcc (3.3.4 and
3.4.3) give a speedup of approximately 30% when the mmx optimisations
are enabled. However with gcc-4.0.0, the performance of the Dirac
encoder with MMX opts enabl
