From: Kishore K <hellokishore@gmail.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Pete Popov <ppopov@embeddedalley.com>,
Ralf Baechle <ralf@linux-mips.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: bal instruction in gcc 3.x
Date: Wed, 20 Jul 2005 14:49:40 +0530 [thread overview]
Message-ID: <f07e6e05072002197b529b72@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61L.0507200955390.30702@blysk.ds.pg.gda.pl>
On 7/20/05, Maciej W. Rozycki <macro@linux-mips.org> wrote:
> On Tue, 19 Jul 2005, Pete Popov wrote:
>
> > Try the attached patch instead.
>
> Apart from other changes why not simply s/bal/jal/? Your proposed code
> is bad if ever to be built to a 64-bit object.
>
In the case of s/bal/jal, I get the warning "No .cprestore pseudo-op
used in PIC code".
Is it safe to ignore this warning ?
On the other hand, if I replace
bal jump_to_label
by
la t9, jump_to_label
jalr t9
I don't see any warning. What could be the reason ?
Can you suggest, what should be done to make the code safe for
building on 64 bit processor.
--kishore
next prev parent reply other threads:[~2005-07-20 9:18 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 [this message]
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
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=f07e6e05072002197b529b72@mail.gmail.com \
--to=hellokishore@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=ppopov@embeddedalley.com \
--cc=ralf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.