From: Zack Weinberg <zack@codesourcery.com>
To: Brad Lucier <lucier@math.purdue.edu>
Cc: jh@suse.cz, gcc@gcc.gnu.org
Subject: Re: Timing information for CFG manipulations
Date: Tue, 16 Oct 2001 21:15:00 -0000 [thread overview]
Message-ID: <20011016211526.J17800@codesourcery.com> (raw)
In-Reply-To: <200110151858.f9FIwIG21154@banach.math.purdue.edu>
On Mon, Oct 15, 2001 at 01:58:18PM -0500, Brad Lucier wrote:
> >
> > - Can you repeat this test with cc1 linked against a profile-
> > instrumented libc,
>
> Unfortunately, on this box libc_p.a seems to be significantly older than
> libc.a and there are link errors.
Weird. What system is this?
> > and libiberty re-built with CFLAGS="-O2 -g -pg"?
>
> I tried this, too, and it links, but I can't get a gmon.out file from
> running the resulting cc1. Perhaps I just don't know how to do such
> things properly.
Hmm, the only thing I can think of is if you forgot to spec CFLAGS
including -pg when re-linking cc1; leave that out and gcrt1.o isn't
loaded, and the profiler never gets started.
zw
next prev parent reply other threads:[~2001-10-16 21:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-13 20:33 Brad Lucier
2001-10-13 21:53 ` Zack Weinberg
2001-10-15 11:58 ` Brad Lucier
2001-10-16 21:15 ` Zack Weinberg [this message]
2001-10-15 12:54 ` Brad Lucier
2001-10-15 14:18 ` Daniel Berlin
2001-10-14 1:18 ` Jan Hubicka
2001-10-14 8:46 ` Brad Lucier
2001-10-14 9:21 ` Daniel Berlin
2001-10-16 7:22 ` Jan Hubicka
2001-10-16 8:25 ` Brad Lucier
2001-10-16 12:46 ` Richard Henderson
2001-10-16 8:01 ` Jan Hubicka
2001-10-16 12:39 ` Brad Lucier
2001-10-16 14:45 ` Jan Hubicka
2001-10-16 16:57 ` Brad Lucier
2001-10-17 12:43 ` Brad Lucier
2001-10-17 13:38 ` Richard Henderson
2001-10-17 14:00 ` Jan Hubicka
2001-10-17 15:38 ` Jan Hubicka
2001-10-17 16:10 ` Richard Henderson
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=20011016211526.J17800@codesourcery.com \
--to=zack@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=jh@suse.cz \
--cc=lucier@math.purdue.edu \
/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).