From: Randolph Chung <randolph@tausq.org>
To: Joel Soete <soete.joel@tiscali.be>
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] c3k panics
Date: Sun, 29 May 2005 18:13:18 -0700 [thread overview]
Message-ID: <20050530011318.GE3050@tausq.org> (raw)
In-Reply-To: <4299F8C2.2060400@tiscali.be>
> #ifndef CONFIG_64BIT
> .macro fixup_branch,lbl
> b \lbl
> .endm
> #else
> .macro fixup_branch,lbl
> ldil L%\lbl, %r1
> ldo R%\lbl(%r1), %r1
> bv,n %r0(%r1)
> .endm
> #endif
These two do the same thing. The 32-bit version is simpler because we
can rely on the linker to do fixups for us if the branch is too far
away. The 64-bit version always uses a long branch sequence to avoid
stub issues with the 64-bit toolchain. In the C code I have simply not
done this (micro-)optimization.
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2005-05-30 1:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-29 1:41 [parisc-linux] c3k panics John David Anglin
2005-05-29 1:50 ` John David Anglin
2005-05-29 22:08 ` Carlos O'Donell
2005-05-29 23:39 ` John David Anglin
2005-05-29 10:32 ` Joel Soete
2005-05-29 17:15 ` Joel Soete
2005-05-30 1:13 ` Randolph Chung [this message]
2005-06-01 14:04 ` Joel Soete
2005-05-29 17:45 ` John David Anglin
[not found] <429A0B7C.3020003@tiscali.be>
2005-05-29 20:49 ` John David Anglin
-- strict thread matches above, loose matches on Subject: below --
2005-05-31 5:41 Joel Soete
2005-05-31 6:26 ` Randolph Chung
2005-06-01 13:11 ` Joel Soete
2005-06-01 13:55 ` John David Anglin
2005-06-01 15:05 Joel Soete
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=20050530011318.GE3050@tausq.org \
--to=randolph@tausq.org \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=soete.joel@tiscali.be \
/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