public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Hildner <christian.hildner@hob.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: loading a kernel module
Date: Wed, 16 Oct 2002 05:52:15 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805170@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805162@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]

Keith Owens schrieb:

> 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.

Keith, Jim,

the source isn't that complex as you might have seen in the length of the objdump output.
The object I have given you is only a small test program to find out the missing linkage for
brl branches. My original program needs brl to branch across virtual pages with a big
difference in the virtual addresses. So the test prog never makes any sence, but shows the
missing R_IA64_PCREL60B nicely.

Christian

PS: Here is the source without any guarantee not to crash ...

[-- Attachment #2: crash.c --]
[-- Type: image/x-xbitmap, Size: 262 bytes --]

  parent reply	other threads:[~2002-10-16  5:52 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
2002-10-16  5:52 ` Christian Hildner [this message]
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-105590709805170@msgid-missing \
    --to=christian.hildner@hob.de \
    --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