From: Keith Owens <kaos@ocs.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: loading a kernel module
Date: Wed, 16 Oct 2002 01:16:08 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805167@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805162@msgid-missing>
On 15 Oct 2002 14:57:07 -0400,
Jim Wilson <wilson@redhat.com> wrote:
>You can get brl instructions by changing "#undef USE_BRL" to "#define USE_BRL"
>in the BINUTILS bfd/elfxx-ia64.c file. I believe that is the change that went
>into the RHL AS toolchain. Then write a large enough program, so that you
>have a call site that is far enough away from its call target to require brl.
You don't need a large program. The test object from Christian Hildner
is about as small as it gets and it still uses brl. Christian, please
post the source of the test object to the list.
0000000000000000 <dummy>:
0: 1d 40 00 00 00 21 [MFB] mov r8=r0
6: 00 00 00 02 00 80 nop.f 0x0
c: 08 00 84 00 br.ret.sptk.many b0;;
0000000000000010 <init_module>:
10: 01 10 11 06 80 05 [MII] alloc r34=ar.pfs,4,3,0
12: LTOFF22 .rodata
16: 10 02 00 62 00 60 mov r33°
1c: 04 08 00 90 addl r35=0,r1;;
20: 1d 18 01 46 18 10 [MFB] ld8 r35=[r35]
22: PCREL21B printk
26: 00 00 00 02 00 00 nop.f 0x0
2c: 08 00 00 50 br.call.sptk.many b0 <init_module+0x10>;;
30: 05 00 00 00 01 00 [MLX] nop.m 0x0
32: PCREL60B dummy
...
3e: 00 c0 00 40 brl.few 30 <init_module+0x20>;;
42: 00 00 00 21 00 10 [MII] mov r8=r0
48: 01 55 00 00 10 0a mov.i ar.pfs=r34
4e: 00 07 1d 00 mov b0=r33
52: 00 00 01 00 00 00 [MFB] nop.m 0x0
58: 00 02 00 80 08 00 nop.f 0x0
5e: 84 00 01 10 br.ret.sptk.many b0;;
next prev parent reply other threads:[~2002-10-16 1:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 12:34 [Linux-ia64] Re: loading a kernel module Keith Owens
2002-10-15 18:57 ` Jim Wilson
2002-10-16 1:16 ` Keith Owens [this message]
2002-10-16 5:52 ` Christian Hildner
2002-10-16 7:04 ` Keith Owens
2002-10-16 7:56 ` Christian Hildner
2002-10-16 9:06 ` Christian Hildner
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=marc-linux-ia64-105590709805167@msgid-missing \
--to=kaos@ocs.com.au \
--cc=linux-ia64@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