From: Ralf Baechle <ralf@oss.sgi.com>
To: Kip Walker <kwalker@broadcom.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: .section problems in entry.S
Date: Sun, 9 Dec 2001 22:18:35 -0200 [thread overview]
Message-ID: <20011209221835.A11737@dea.linux-mips.net> (raw)
In-Reply-To: <3C1104D4.F700768A@broadcom.com>; from kwalker@broadcom.com on Fri, Dec 07, 2001 at 10:05:08AM -0800
On Fri, Dec 07, 2001 at 10:05:08AM -0800, Kip Walker wrote:
> I just investigated assembler warnings coming from
> arch/mips/kernel/entry.S (checked out as of 12/07 00:00 UTC), and
> noticed the following. After expanding macros, you get something like:
>
> .text
>
> .section ".text.init" (from __INIT)
>
> .data (from PANIC)
> .previous (from PANIC)
> --> section is now .text.init
>
> .previous (from __FINIT)
> --> section is now .data, not .text as intended.
>
> Perhaps .pushsection and .popsection should be used in some or all
> macros like this?
>
> Or am I smoking crack?
Certainly not. The problem is known and so far I've just hacked around
it more or less elegant. But it's a trap and so I think we've got good
reasons to force people to upgrade to a newer assembler than the current
minimal version. The question is which - I don't like frequent tool
upgrades.
Ralf
next prev parent reply other threads:[~2001-12-10 1:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 18:05 .section problems in entry.S Kip Walker
2001-12-10 0:18 ` Ralf Baechle [this message]
2001-12-10 16:03 ` Maciej W. Rozycki
2001-12-13 20:45 ` Ralf Baechle
2001-12-13 21:12 ` Thiemo Seufer
2001-12-13 21:27 ` Daniel Jacobowitz
2001-12-13 22:13 ` Thiemo Seufer
2001-12-13 22:21 ` Daniel Jacobowitz
2001-12-13 21:28 ` Daniel Jacobowitz
2001-12-13 21:37 ` Ralf Baechle
2001-12-13 21:41 ` Daniel Jacobowitz
2001-12-14 14:47 ` Maciej W. Rozycki
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=20011209221835.A11737@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=kwalker@broadcom.com \
--cc=linux-mips@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.