All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hasjim Williams" <openembedded-devel@lists.futaris.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: iwmmxt optimization and soft float in OE on PXA270
Date: Fri, 21 Mar 2008 08:14:16 +1000	[thread overview]
Message-ID: <1206051256.5975.1243541279@webmail.messagingengine.com> (raw)
In-Reply-To: <1206017175.4700.8.camel@hammer.suse.cz>


On Thu, 20 Mar 2008 13:46:15 +0100, "Stanislav Brabec" <utx@penguin.cz>
said:
> Hasjim Williams wrote:
> 
> > You won't be able to use iwmmxt with everything.  The unwind / exception
> > support for iwxmmt isn't there in gcc.  Anything using C++ exceptions
> > won't work correctly.
> 
> So plain C binaries (e. g. kernel) are OK? And
> c++ -march=iwmmxt -fno-exceptions as well?

You can try this for C++ with -fno-exceptions, but I've never tried
it...

> > I could write/test these patches, I guess, but the only PXA270 machine
> > that I have access to is a HTC Magician (XDA Mini).
> 
> It would be very nice. I could test them on my Zaurus, if you send me
> some C++ testcase (or name of application to test it on).

It'd be good if you could run the tests, before we generate the
patches... 

gcc has a built in testcase system, dejagnu:
http://lists.gnu.org/archive/html/dejagnu/2006-04/msg00008.html explains
how to set it up and run it.
http://gcc.gnu.org/onlinedocs/libstdc++/test.html and 

e.g. FROM:
openembedded/build/tmp/work/armv4t-angstrom-linux-gnueabi/gcc-cross-4.1.2-r13/gcc-4.1.2/build.i686-linux.arm-angstrom-linux.arm-angstrom-linux-gnueabi
$ make check-gcc RUNTESTFLAGS="normal.exp --target_board=pxa270-linux"

I think the C++ support you're looking to test is in "normal.exp" .  You
should get a gcc.log and gcc.sum at the end, saying what tests
passed/failed.

$ make check
Will do a complete test of everything, and will probably take at least 8
hrs - day on a pxa270, I would think.

You'll only need dropbear or some other ssh server, so even a
minimal-image should be enough on your pxa27x machine.
 
> The last missing thing - iwmmxt support in qemu - was already written by
> Andrzej Zaborowski.

Is this "qemu-pxa270-and-more.patch" or is there something newer?  Has
this been put into OE's buildtree?

NB, Not sure what you're using to profile the speedups, but there is:

gcov:
http://gcc.gnu.org/onlinedocs/gcc/Gcov.html#Gcov

and gprof:
http://www.gnu.org/software/binutils/manual/gprof-2.9.1/gprof.html



  reply	other threads:[~2008-03-20 22:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-02 21:47 iwwmmxt optimization and soft float in OE on PXA270 Stanislav Brabec
2008-03-03  7:29 ` Koen Kooi
2008-03-03 10:48   ` Stanislav Brabec
2008-03-04  7:26     ` Khem Raj
2008-03-04 11:18       ` Stanislav Brabec
2008-03-04 20:32         ` Stanislav Brabec
2008-03-20  6:03   ` iwmmxt " Hasjim Williams
2008-03-20 12:46     ` Stanislav Brabec
2008-03-20 22:14       ` Hasjim Williams [this message]
2008-03-21 22:52         ` Khem Raj
2008-03-23 18:01         ` iwmmxt optimization on PXA270 (dejagnu test report) Stanislav Brabec
2008-03-26  1:39           ` Hasjim Williams
2008-04-01  0:27             ` Hasjim Williams
2008-04-01  3:21               ` Hasjim Williams

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=1206051256.5975.1243541279@webmail.messagingengine.com \
    --to=openembedded-devel@lists.futaris.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.