public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@snake.cs.utah.edu>
To: gas2@cygnus.com
Subject: Re: new changes in gprof, bfd, gas
Date: Tue, 07 Feb 1995 15:24:00 -0000	[thread overview]
Message-ID: <7021.792199472@snake.cs.utah.edu> (raw)
In-Reply-To: <199502072243.RAA18929@kr-pc.cygnus.com>

  In message < 199502072243.RAA18929@kr-pc.cygnus.com > you write:
  > 
  > Some of these might be of interest to people:
  > 
  > >From David Mosberger-Tang, revised gprof support.  Now alpha-osf
  > configurations are supported, and line-level profiling is available.
  > The latter requires bfd_find_nearest_line; currently at least ELF and
  > SOM are missing this support, and the SOM code aborts when it is
  > called.  Lots of other changes too; see gprof/NOTES for details.
I notice some problems with the new code:

core_init looks for sections by name.  That is *very* bad for
formats such as SOM & ELF.

The specific problem I see is it looks for $CODE$; well, in
SOM there may be hundreds of $CODE$ sections in a file, and
even if you get all of them you're still going to miss
other sections with code in them like $MILLICODE$.

[ Of course the old code had the same behavior in that it just
  looked for .text; but we never made use of the info for
  SOM/HPUX.  From my quick reading the new code actually wants
  to use information it gathers about sections & their contents. ]

Can someone run this mess through indent?  GNU has formatting
standards, we might as well try to adhere to them.


Jeff





  parent reply	other threads:[~1995-02-07 15:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-02-07 14:43 raeburn
1995-02-07 15:10 ` Jeffrey A Law
1995-02-07 16:06   ` raeburn
1995-02-07 16:17     ` Jeffrey A Law
1995-02-07 15:24 ` Jeffrey A Law [this message]
1995-02-07 16:56   ` Richard Stallman
1995-02-07 16:59     ` Jeffrey A Law
1995-02-07 20:34       ` Richard Stallman
1995-02-07 21:36         ` Jeffrey A Law
1995-02-07 16:22 David Mosberger-Tang

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=7021.792199472@snake.cs.utah.edu \
    --to=law@snake.cs.utah.edu \
    --cc=gas2@cygnus.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).