public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Eli Carter <eli.carter@inet.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: .section ... "ax" vs  #alloc, #execinstr
Date: Wed, 16 Apr 2003 00:05:45 +0100	[thread overview]
Message-ID: <20030416000545.H32468@flint.arm.linux.org.uk> (raw)
In-Reply-To: <3E9C664A.503@inet.com>; from eli.carter@inet.com on Tue, Apr 15, 2003 at 03:06:34PM -0500

On Tue, Apr 15, 2003 at 03:06:34PM -0500, Eli Carter wrote:
> Some of the assembly files use
> .section        ".start", "ax"
> and others use
> .section ".start", #alloc, #execinstr
> (and not just for .start, try
> find -name \*.S | xargs grep -e '\.section'
> )
> 
> These appear to be equivelent, if not somebody clue me in please. :) 
> Which is the prefered form?  The latter seems to provide a bit more for 
> the human, so I'd vote that direction... ;)

I guess you're asking about the IOP3xx stuff.

info as
mp<tab>
msec<tab>

gives all the details.  To summarise though:

	"a" or "#alloc" - the section is allocatable
	"x" or "#execinstr" - the section is executable

"ax" seems to be what Linus uses.  I used to use the long versions, but
changed to the shorter version - less characters to type, but still
fairly readable.  After all, you don't catch people trying to make ls
report stuff like:

file, user read write execute, group read execute, other read execute,
2 links, owner root, group root, 44 kibytes, modified xxxx, name "foo"

(or I hope you don't! 8))

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2003-04-15 22:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-15 20:06 .section ... "ax" vs #alloc, #execinstr Eli Carter
2003-04-15 23:05 ` Russell King [this message]
2003-04-15 23:06 ` Daniel Jacobowitz

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=20030416000545.H32468@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=eli.carter@inet.com \
    --cc=linux-kernel@vger.kernel.org \
    /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