public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan Hubicka <jh@suse.cz>
To: Nathan Sidwell <nathan@codesourcery.com>
Cc: Jan Hubicka <jh@suse.cz>, Qiong Cai <qiongc@cse.unsw.edu.au>,
	gcc@gcc.gnu.org
Subject: Re: new edge coverage profiler on gcc 3.3
Date: Mon, 14 Oct 2002 09:19:00 -0000	[thread overview]
Message-ID: <20021014151556.GB14971@kam.mff.cuni.cz> (raw)
In-Reply-To: <3DAACAA7.9020209@codesourcery.com>

> Jan Hubicka wrote:
> 
> >It is complete and it should produce .da files.
> >Does the program crash at the end?  There seems to be common collision
> >with the routines in glibc handling of profiler format.
> do you think we should rename those routines for 3.3?
> 
> (Separately) I think we should break them out of libgcc into a libgcov,
> so that they work with a shared link of libgcc. We can have a spec which
> turns -fcoverage into -lgcov. This is appropriate for 3.4, but is it
> too for 3.3?
I hope so.
> 
> Oh, yes. Does your recent change to use the mangled name for functions
> require tweaks in the stuff I did on b-i-b?
Hope it will merge easilly.

Honza
> 
> nathan
> 
> -- 
> Dr Nathan Sidwell   ::   http://www.codesourcery.com   ::   CodeSourcery LLC
>          'But that's a lie.' - 'Yes it is. What's your point?'
> nathan@codesourcery.com : http://www.cs.bris.ac.uk/~nathan/ : nathan@acm.org
> 

  reply	other threads:[~2002-10-14 15:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-12 20:05 Qiong Cai
2002-10-13 15:49 ` Jan Hubicka
2002-10-14  9:09   ` Nathan Sidwell
2002-10-14  9:19     ` Jan Hubicka [this message]
2002-10-14 23:07     ` Mark Mitchell
2002-10-15 11:55     ` J.T. Conklin
2002-10-15 12:02       ` Nathan Sidwell

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=20021014151556.GB14971@kam.mff.cuni.cz \
    --to=jh@suse.cz \
    --cc=gcc@gcc.gnu.org \
    --cc=nathan@codesourcery.com \
    --cc=qiongc@cse.unsw.edu.au \
    /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).