From: Ralf Baechle <ralf@linux-mips.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-arch@vger.kernel.org, Jan Beulich <JBeulich@novell.com>
Subject: Re: Fw: [PATCH] abstract type/size specification for assembly
Date: Wed, 1 Feb 2006 13:50:03 +0000 [thread overview]
Message-ID: <20060201135002.GA6386@linux-mips.org> (raw)
In-Reply-To: <20060131143149.35db2e02.akpm@osdl.org>
On Tue, Jan 31, 2006 at 02:31:49PM -0800, Andrew Morton wrote:
> OK?
No.
> diff -puN include/linux/linkage.h~abstract-type-size-specification-for-assembly include/linux/linkage.h
> --- 25/include/linux/linkage.h~abstract-type-size-specification-for-assembly Tue Jan 31 14:30:58 2006
> +++ 25-akpm/include/linux/linkage.h Tue Jan 31 14:30:58 2006
> @@ -39,6 +39,11 @@
> ALIGN; \
> name:
>
> +#define ENDPROC(name) \
> + .type name, @function; \
> + END(name)
> +#define END(name) \
> + .size name, .-name
>
> #endif
No. On MIPS we need a .end directive as well; since the dawn of Linux I
have the following in include/asm-mips/asm.h:
#define END(function) \
.end function; \
.size function,.-function
And while we're at it, the ENTRY definition there isn't usable on MIPS
either; we need two different definitions for leaf and no-leaf functions
which again are in asm.h:
/*
* LEAF - declare leaf routine
*/
#define LEAF(symbol) \
.globl symbol; \
.align 2; \
.type symbol,@function; \
.ent symbol,0; \
symbol: .frame sp,0,ra
/*
* NESTED - declare nested routine entry point
*/
#define NESTED(symbol, framesize, rpc) \
.globl symbol; \
.align 2; \
.type symbol,@function; \
.ent symbol,0; \
symbol: .frame sp, framesize, rpc
Ralf
prev parent reply other threads:[~2006-02-02 11:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 22:31 Fw: [PATCH] abstract type/size specification for assembly Andrew Morton
2006-02-01 7:36 ` Andi Kleen
2006-02-01 8:32 ` Russell King
2006-02-01 8:49 ` Andi Kleen
2006-02-01 9:09 ` Russell King
2006-02-01 11:40 ` Jan Beulich
2006-02-08 16:11 ` Jan Beulich
2006-02-01 13:50 ` Ralf Baechle [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=20060201135002.GA6386@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=JBeulich@novell.com \
--cc=akpm@osdl.org \
--cc=linux-arch@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