From: Kurt Roeckx <Q@ping.be>
To: alan@lxorguk.ukuu.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: _stext and _etext in 2.2.18pre20
Date: Wed, 8 Nov 2000 14:42:53 +0100 [thread overview]
Message-ID: <20001108144252.A6071@ping.be> (raw)
I once complained about the s390 port not compiling because
_stext had conflicting types.
You seem to have changed include/asm/irq.h then, adding [] to it,
like it is in kernel/ksyms.c.
I just did a little grepping, And saw this:
./init/main.c:extern char _stext, _etext;
./kernel/ksyms.c:extern char _stext[], _etext[];
./include/asm-s390/irq.h:extern char _stext[];
./arch/i386/kernel/irq.h:extern char _stext, _etext;
./arch/alpha/kernel/traps.c: extern unsigned long
_stext, _etext;
./arch/alpha/kernel/irq.h:extern char _stext;
./arch/sparc/kernel/sun4d_smp.c: extern int
_stext;
./arch/sparc/kernel/sun4m_smp.c: extern int
_stext;
./arch/sparc/mm/btfixup.c:extern unsigned int _stext[], _end[],
__start___ksymtab[], __stop___ksymtab[];
./arch/sparc/ap1000/timer.c: extern int _stext;
./arch/mips/kernel/traps.c: extern char _stext, _etext;
./arch/mips/kernel/time.c: extern int
_stext;
./arch/ppc/mm/init.c:extern char etext[], _stext[];
./arch/m68k/kernel/time.c: extern int _stext;
./arch/sparc64/kernel/smp.c: extern int _stext;
./arch/arm/kernel/setup.c:extern int _stext, _text, _etext,
_edata, _end;
./arch/arm/kernel/time.c: extern int _stext;
./arch/arm/mm/init.c:extern char _etext, _stext, _edata,
__bss_start, _end;
As you can see, most of them don't have the [], but some do.
Others are (still?) signed or unsigned, int or long's.
I think all of them should be pointers, it doesn't make much
sense for them to be a char, altho most are just chars.
Doing the same in 2.4.0-test10, shows about the same.
What should be done with this?
Kurt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2000-11-08 13:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20001108144252.A6071@ping.be \
--to=q@ping.be \
--cc=alan@lxorguk.ukuu.org.uk \
--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