public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Danny Backx <danny.backx@scarlet.be>
Cc: Ben Elliston <bje@au1.ibm.com>,
	Sanjay Chadha <sanjay@s5systems.com>,
	        binutils@sourceware.org
Subject: Re: [PATCH] enabling gprof for cross builds
Date: Fri, 20 Apr 2007 14:28:00 -0000	[thread overview]
Message-ID: <4628C817.6030303@redhat.com> (raw)
In-Reply-To: <1176390019.14038.54.camel@dannypc>

Hi Danny,

> I have a patch that allows you to specify a different directory than the
> host source directory.
> 
> That means :
> - you compile on a PC, sources in e.g. /home/danny/src/prog.c
> - by default, gcc compiles in a path /home/danny/src in which the
>   executable will try to store its profile information
> - that is not always present on the mobile device
> - there is a way to change this directory at run time, but that
>   isn't always easy (it isn't on CE)
> - so I've added a way to specify a different directory at compile
>   time, meaning I can override the directory that gcc puts in the
>   object file
> 
> I've been wanting to submit the code but didn't get around to it yet.
> 
> Should I clean it up and submit ?

This does sound interesting, but isn't this a patch to gcc rather than 
to gprof ?  If so then it should be submitted to the gcc-patches list 
rather than the binutils list.  Either way though, cleaning it up and 
submitting it would be a good thing to do.

Cheers
   Nick

  parent reply	other threads:[~2007-04-20 14:03 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
2007-04-20 14:28     ` Nick Clifton [this message]
  -- 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=4628C817.6030303@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=bje@au1.ibm.com \
    --cc=danny.backx@scarlet.be \
    --cc=sanjay@s5systems.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).