From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001959] New: ARM call-graph profiling
Date: Fri, 14 Mar 2014 11:34:00 -0000 [thread overview]
Message-ID: <bug-1001959-104@http.bugs.ecos.sourceware.org/> (raw)
Please do not reply to this email, use the link below.
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001959
Bug ID: 1001959
Summary: ARM call-graph profiling
Product: eCos
Version: CVS
Target: Other (please specify)
Architecture/Host ARM
OS:
Status: NEW
Severity: enhancement
Priority: low
Component: Patches and contributions
Assignee: unassigned@bugs.ecos.sourceware.org
Reporter: john@dallaway.org.uk
CC: ecos-patches@ecos.sourceware.org
Created attachment 2484
--> http://bugs.ecos.sourceware.org/attachment.cgi?id=2484&action=edit
arm-mcount-140314.patch
ARM mcount functions to support call-graph profiling.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2014-03-14 11:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 11:34 bugzilla-daemon [this message]
2014-03-14 21:39 ` [Bug 1001959] " bugzilla-daemon
2014-03-15 20:15 ` bugzilla-daemon
2014-03-15 22:12 ` bugzilla-daemon
2014-03-16 19:45 ` bugzilla-daemon
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=bug-1001959-104@http.bugs.ecos.sourceware.org/ \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-patches@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).