9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Anthony Martin <ality@pbrane.org>
To: comeau@comeaucomputing.com,
	Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] nm "L symbols"
Date: Wed,  4 May 2011 05:16:51 -0700	[thread overview]
Message-ID: <20110504121651.GA29768@dinah> (raw)
In-Reply-To: <ip4ppn$5um$1@panix3.panix.com>

Greg Comeau <comeau@panix.com> once said:
> man nm shows a symbol type of L that is possible denoting it as
> a "leaf function text segment symbol".   Often a leaf function
> is distinguished by being at the end of a call hierarchy and
> can sometimes yield difference in code generation regarding
> stack space and such.  Is this the case here?  If so,
> then a L is otherwise a T (and an l a t), or is there some
> other differences?

You've got it.  The Plan 9 linkers for RISC-y
architectures will output these leaf symbols.

  Anthony



      reply	other threads:[~2011-05-04 12:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-04 11:40 Greg Comeau
2011-05-04 12:16 ` Anthony Martin [this message]

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=20110504121651.GA29768@dinah \
    --to=ality@pbrane.org \
    --cc=9fans@9fans.net \
    --cc=comeau@comeaucomputing.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 NNTP newsgroup(s).