From: Thiemo Seufer <ths@networkno.de>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Alexander Voropay <alec@artcoms.ru>,
Kishore K <hellokishore@gmail.com>,
linux-mips@linux-mips.org
Subject: Re: bal instruction in gcc 3.x
Date: Wed, 20 Jul 2005 15:25:24 +0200 [thread overview]
Message-ID: <20050720132524.GL2071@hattusa.textio> (raw)
In-Reply-To: <Pine.LNX.4.61L.0507201347350.30702@blysk.ds.pg.gda.pl>
Maciej W. Rozycki wrote:
> On Wed, 20 Jul 2005, Alexander Voropay wrote:
>
> > 3) AFAIK (correct me), there is no MIPS-specific RELOC type for
> > the "branch" instruction format in the BFD, so "bal" to the *external*
> > symbols is impossible.
>
> There is a reloc called BFD_RELOC_16_PCREL_S2 which is used for branches
> by BFD internally, but unfortunately the original SysV ELF supplement for
> MIPS failed to define an appropriate relocation for this purpose (there is
> useless R_MIPS_PC16, though), so there is nothing to map this internal
> relocation to. There were discussions as to whether reuse R_MIPS_PC16 for
> branches or not. Unfortunately I don't remember the conclusion -- you'd
> have to find it out yourself.
It is ok to reuse it, but nobody has done the work yet.
Thiemo
next prev parent reply other threads:[~2005-07-20 13:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 16:30 bal instruction in gcc 3.x Kishore K
2005-07-19 16:44 ` Ralf Baechle
2005-07-19 17:19 ` Kishore K
2005-07-19 19:53 ` Pete Popov
2005-07-20 8:59 ` Maciej W. Rozycki
2005-07-20 9:17 ` Thiemo Seufer
2005-07-20 9:47 ` Maciej W. Rozycki
2005-07-20 9:19 ` Kishore K
2005-07-20 9:52 ` Maciej W. Rozycki
2005-07-20 12:39 ` Alexander Voropay
2005-07-20 12:39 ` Alexander Voropay
2005-07-20 12:54 ` Maciej W. Rozycki
2005-07-20 13:24 ` Alexander Voropay
2005-07-20 13:24 ` Alexander Voropay
2005-07-20 13:25 ` Thiemo Seufer [this message]
2005-07-20 12:54 ` Thiemo Seufer
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=20050720132524.GL2071@hattusa.textio \
--to=ths@networkno.de \
--cc=alec@artcoms.ru \
--cc=hellokishore@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.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