From: Keith Owens <kaos@ocs.com.au>
To: paulus@linuxcare.com.au
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Where does ppc define __start___ksymtab?
Date: Thu, 03 Aug 2000 18:03:13 +1000 [thread overview]
Message-ID: <29943.965289793@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Thu, 03 Aug 2000 16:13:46 +1000." <14729.3482.592712.436379@argo.linuxcare.com.au>
On Thu, 3 Aug 2000 16:13:46 +1000 (EST),
Paul Mackerras <paulus@linuxcare.com.au> wrote:
>> I have been trying to find where ppc defines __start___ksymtab and
>> __stop___ksymtab symbols. These delimit the __ksymtab entries for
>> module symbols. On every other architecture that supports modules,
>> arch/xxx/vmlinux.lds contains lines like this
>>
>> __start___ksymtab = .; /* Kernel symbol table */
>> __ksymtab : { *(__ksymtab) }
>> __stop___ksymtab = .;
>>
>> I can find no equivalent lines for ppc in a stock 2.4.0-test5 source
>> tree yet ppc obviously defines them somewhere. But where?
>
>I think they must be defined automagically by the linker. They aren't
>defined explicitly anywhere but we still end up with a __ksymtab
>section with the __start___ksymtab and __stop___ksymtab symbols
>defined at the beginning and end of it.
>
>We can add those lines if you like, that's no problem.
Please add them. It makes the ppc vmlinux.lds more consistent with the
other archs that support modules.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-03 8:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-01 6:40 Where does ppc define __start___ksymtab? Keith Owens
2000-08-02 20:18 ` Geert Uytterhoeven
2000-08-03 11:28 ` Gabriel Paubert
2000-08-03 11:40 ` Keith Owens
2000-08-03 6:13 ` Paul Mackerras
2000-08-03 8:03 ` Keith Owens [this message]
2000-08-03 9:58 ` Gabriel Paubert
2000-08-03 11:43 ` Keith Owens
2000-08-03 12:01 ` Gabriel Paubert
2000-08-03 12:18 ` Keith Owens
2000-08-03 12:31 ` Gabriel Paubert
2000-08-03 12:27 ` Keith Owens
2000-08-03 13:08 ` Franz Sirl
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=29943.965289793@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@linuxcare.com.au \
/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;
as well as URLs for NNTP newsgroup(s).