From: Patrice Bouchand <pb_fwd_list@yahoo.fr>
To: WolfgangDenk <wd@denx.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: mcpu options for AMCC440 with fpu
Date: Sat, 24 Feb 2007 07:44:45 +0100 [thread overview]
Message-ID: <1172299485.2993.8.camel@localhost.localdomain> (raw)
In-Reply-To: <20070223225818.8DF743525B0@atlas.denx.de>
Indeed ! I was waiting for warnings or errors while compiling to tell me
I was doing something wrong but I should not.
Thanks for your time.
Patrice
> In message <600461.55072.qm@web23412.mail.ird.yahoo.com> you wrote:
> >
> > I was searching for the best mcpu option for amcc440, compiling and running a small program you can find here:
> > http://magnux.free.fr/gcc/mandelbrot.c. My distro is a ppc fedora core 6, and results are obviously the same using DENX4.0.
>
> In general, you should need to meddle much with such options; the ELDK
> default settings are usually OK.
>
> > --------------------
> > -bash-3.00# gcc -O2 ./mandelbrot.c -o ./mandelbrot && time ./mandelbrot && rm -f ./mandelbrot
> >
> > real 1m15.059s
> > user 1m14.996s
> > sys 0m0.060s
> > -bash-3.00# gcc -O2 -mcpu=440 ./mandelbrot.c -o ./mandelbrot && time ./mandelbrot && rm -f ./mandelbrot
> >
> > real 0m39.606s
> > user 0m39.552s
> > sys 0m0.028s
> > -bash-3.00# gcc -O2 -mcpu=440fp ./mandelbrot.c -o ./mandelbrot && time ./mandelbrot && rm -f ./mandelbrot
> >
> > real 1m15.016s
> > user 1m14.988s
> > sys 0m0.024s
> > -bash-3.00# gcc -O2 -msoft-float ./mandelbrot.c -o ./mandelbrot && time ./mandelbrot && rm -f ./mandelbrot
> >
> > real 0m39.577s
> > user 0m39.544s
> > sys 0m0.032s
>
> This looks to me as if you have been runing all these tests in the
> SAME environment, probably the /opt/eldk/ppc_4xx root file system,
> which is soft-float based. You must not do this.
>
> For tests with FP instructions, you MUST use the /opt/eldk/ppc_4xxFP
> root file system. For tests with soft-float, you MUST use the
> /opt/eldk/ppc_4xx root file system.
>
> You CANNOT link an application build with one settings against
> libraries using other settings, or you will run into trouble. You
> would probably have seen the problems if you had used any test where
> the results of the calculations would have been visible.
>
>
> > * I do not explain why not using FPU gives better results ?
>
> Because you did not run the tests you thought yoiu were running.
>
> > * mcpu option seems to not have any effect ?
>
> Use "gcc -v" to see exactly which options get passed to the compiler
> stages.
>
> > * My third test was to compile and run mplayer.
> > - With default options (no mcpu specified), my test mpeg was smooth.
> > - With mcpu=440fp, my test mpeg was not smooth.
> >
> > Can anybody bring me some lights about the right gcc mcpu option for amcc440 ?
>
> Just use the defaults, unless you know exactly what you are doing.
>
> Best regards,
>
> Wolfgang Denk
>
next prev parent reply other threads:[~2007-02-24 7:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 8:45 mcpu options for AMCC440 with fpu Patrice Bouchand
2007-02-21 19:47 ` Patrice Bouchand
2007-02-21 21:35 ` Magnus Hjorth
2007-02-22 6:57 ` RE : " Patrice Bouchand
2007-02-23 22:58 ` Wolfgang Denk
2007-02-24 6:44 ` Patrice Bouchand [this message]
2007-02-24 20:20 ` Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1172299485.2993.8.camel@localhost.localdomain \
--to=pb_fwd_list@yahoo.fr \
--cc=linuxppc-embedded@ozlabs.org \
--cc=wd@denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).