On Thu, 2007-05-10 at 21:36 +0200, Danny Backx wrote:
> Attached is a patch with a small amount of documentation but lacking a
> ChangeLog entry. I'm sending it now already for you to comment on.
Please submit patches to the gcc-patches mailing list, not the main gcc
list. Oh, and please include
On Fri, 2007-05-04 at 09:49 +1000, Ben Elliston wrote:
> On Thu, 2007-05-03 at 19:55 +0200, Danny Backx wrote:
>
> > Ok, a command line option is what I have. I'll try to clean up my
> > patch shortly, and see if it still applies cleanly in a recent gcc
> > tree. Our current version is based on gc
On Thu, 2007-05-03 at 19:55 +0200, Danny Backx wrote:
> Ok, a command line option is what I have. I'll try to clean up my
> patch shortly, and see if it still applies cleanly in a recent gcc
> tree. Our current version is based on gcc-4.1.0. Or is a patch against
> that ok ?
This feature would no
On Tue, 2007-05-01 at 09:27 +1000, Ben Elliston wrote:
> On Mon, 2007-04-23 at 22:16 +0200, Danny Backx wrote:
>
> > Gcov normally puts the files where it writes profiling information in
> > the source directory. In a cross-development environment, that directory
> > isn't always available.
>
> S
On Mon, 2007-04-23 at 22:16 +0200, Danny Backx wrote:
> Gcov normally puts the files where it writes profiling information in
> the source directory. In a cross-development environment, that directory
> isn't always available.
So I discovered when debugging testsuite failures on a remote target :
I am working on the cegcc project (http://cegcc.sourceforge.net), which
bundles a bunch of the GNU development tools to produce a
cross-development environment for ARM devices running Windows CE. The
development hosts supported are Linux and Cygwin.
Gcov normally puts the files where it writes pro
