From: Ralf Baechle <ralf@linux-mips.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ulrich Eckhardt <eckhardt@satorlaser.com>,
Linux/MIPS Development <linux-mips@linux-mips.org>
Subject: Re: conflicting declaration of prom_getcmdline()
Date: Mon, 4 Apr 2005 12:37:03 +0100 [thread overview]
Message-ID: <20050404113703.GA8538@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0504041318590.14107@numbat.sonytel.be>
On Mon, Apr 04, 2005 at 01:20:15PM +0200, Geert Uytterhoeven wrote:
> IIRC, there are architectures (alpha?) where __init does matter for prototypes
> because a different jump type is used depending on the sections of the caller
> and callee.
MIPS gcc doesn't do such optimizations - and we'd expect no advantage from
it either because the range of R_MIPS_26 relocations used for jump
instructions is 256MB - unless somebody hits the special case where this
256MB boundary is going straight through the kernel in which case
-mlong-jump would be required anyway, __init or not.
Ralf
prev parent reply other threads:[~2005-04-04 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 8:28 conflicting declaration of prom_getcmdline() Ulrich Eckhardt
2005-04-04 6:21 ` Ralf Baechle
2005-04-04 11:20 ` Geert Uytterhoeven
2005-04-04 11:37 ` 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=20050404113703.GA8538@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=eckhardt@satorlaser.com \
--cc=geert@linux-m68k.org \
--cc=linux-mips@linux-mips.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