public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: moktar_bouain <moktarbouain@yahoo.fr>
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] measure the execution time of each thread
Date: Thu, 28 Apr 2011 02:39:00 -0000	[thread overview]
Message-ID: <31493032.post@talk.nabble.com> (raw)
In-Reply-To: <4DB56AB2.50109@mlbassoc.com>


>Looks like HAL_CLOCK_READ() isn't working on your hardware.
>What's your target hardware?  Is it part of the public eCos tree?
Hi Gary,
I used the  processor leon3 (SPARC) with the platform Digilent-XUP.
I tried with HAL_CLOCK_READ(), and i added the following lines:
HAL_CLOCK_READ(&t1);
HAL_CLOCK_READ(&t2);
printf("t1 is: %lu \n",t1);
printf("t2 is: %lu \n",t2);
printf("t2-t1 is: %d\n",t2-t1);

The result is:
t1 is:333
t2 is:294
t2-t1 is:-39


-- 
View this message in context: http://old.nabble.com/measure-the-execution-time-of-each-thread-tp31407684p31493032.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2011-04-28  2:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-15 17:11 moktar_bouain
2011-04-18 17:03 ` Michael Bergandi
2011-04-18 22:01   ` moktar_bouain
2011-04-18 22:50     ` Gary Thomas
2011-04-18 23:32       ` moktar_bouain
2011-04-19 11:07         ` Gary Thomas
2011-04-22 23:00           ` moktar_bouain
2011-04-23 14:33             ` Gary Thomas
2011-04-23 15:07               ` moktar_bouain
2011-04-23 17:11                 ` Gary Thomas
2011-04-24 22:22                   ` moktar_bouain
2011-04-25 12:36                     ` Gary Thomas
2011-04-28  2:39                       ` moktar_bouain [this message]
2011-04-19  6:06 ` Yurij Grechishhev

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=31493032.post@talk.nabble.com \
    --to=moktarbouain@yahoo.fr \
    --cc=ecos-discuss@ecos.sourceware.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).