From: Danny Backx <danny.backx@scarlet.be>
To: John Tytgat <John.Tytgat@aaug.net>
Cc: binutils@sources.redhat.com
Subject: Re: [PATCH] enabling gprof for cross builds
Date: Thu, 19 Apr 2007 21:54:00 -0000 [thread overview]
Message-ID: <1177011622.14038.138.camel@dannypc> (raw)
In-Reply-To: <67338dd24e.Jo@hobbes.bass-software.com>
[-- Attachment #1: Type: text/plain, Size: 1480 bytes --]
I need to apologise, I probably anwered the wrong question.
I've done stuff for gprof and gcov on the cegcc project.
For gprof, the tweaks are now in a directory src/profile/profile in our
svn; for gcov, they are in (roughly) src/gcc/gcc/*gcov* .
The gcov stuff allows you to specify a different directory on the gcc
command line, I didn't do this for gprof.
Does any of this sound interesting ?
I've been wanting to submit the gcov tweaks but I need to find the time.
Also part of the process is that I need to ask the maintainers how to
preferably get the information into the tool : should this via a gcc
command line option, an environment variable, or both.
Danny
On Thu, 2007-04-12 at 21:39 +0100, John Tytgat wrote:
> In message <1176390019.14038.54.camel@dannypc>
> Danny Backx <danny.backx@scarlet.be> wrote:
>
> > [ cross-compiled gprof ]
> > I played with this a while ago for cegcc, and got it to work. (Host
> > environment is either linux or cygwin, target is Windows CE on ARM.)
> >
> > I have a patch that allows you to specify a different directory than the
> > host source directory.
> >
> > That means :
> > [...]
> >
> > I've been wanting to submit the code but didn't get around to it yet.
> >
> > Should I clean it up and submit ?
>
> I would be interested to see this commited.
>
> Thanks for the effort,
> John.
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-04-19 19:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 17:46 Sanjay Chadha
2007-04-12 4:08 ` Ben Elliston
2007-04-12 15:13 ` Danny Backx
2007-04-13 1:09 ` John Tytgat
2007-04-19 21:54 ` Danny Backx [this message]
2007-04-20 14:28 ` Nick Clifton
-- strict thread matches above, loose matches on Subject: below --
2006-05-08 23:48 Mark Shinwell
2006-05-09 1:38 ` Daniel Jacobowitz
2006-05-09 2:05 ` Ben Elliston
2006-05-09 20:33 ` Mark Shinwell
2006-05-24 12:31 ` Mark Shinwell
2006-05-24 14:28 ` Daniel Jacobowitz
2006-05-24 17:09 ` Mark Shinwell
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=1177011622.14038.138.camel@dannypc \
--to=danny.backx@scarlet.be \
--cc=John.Tytgat@aaug.net \
--cc=binutils@sources.redhat.com \
/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).