public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] gettimeoffset for 2.5.67
Date: Tue, 13 May 2003 06:44:37 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723705749@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705684@msgid-missing>

>>>>> On 12 May 2003 22:05:02 -0400, Jes Sorensen <jes@wildopensource.com> said:

  Jes> As for the instruction bundling, yes of course I checked that, how can
  Jes> you ask ;-) The patch results in a total of three nops before the
  Jes> branch, however no matter how I move it around, getting rid of those
  Jes> doesn't seem to be possible (feel free to challenge me on that one).

This:

+	and r2=IA64_SAL_PLATFORM_FEATURE_ITC_DRIFT,r2
 	;;
+	cmp.ne p8, p0=0, r2
+(p8)	br.spnt.many fsys_fallback_syscall


can be shortened to:

	tbit.nz p8, p0=IA64_SAL_PLATFORM_FEATURE_ITC_DRIFT_BIT, r2
(p8)	br.spnt.many fsys_fallback_syscall

Might make it a bit easier to schedule things around (just add foo_BIT
numbers for all the SAL_PLATFORM_FEATURE bits and then define the
masks in terms of these bit numbers).

Sorry I didn't catch this previously.

	--david


  parent reply	other threads:[~2003-05-13  6:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-08 16:44 [Linux-ia64] gettimeoffset for 2.5.67 Jes Sorensen
2003-05-08 22:24 ` David Mosberger
2003-05-11 17:54 ` Jes Sorensen
2003-05-12 23:40 ` David Mosberger
2003-05-13  2:05 ` Jes Sorensen
2003-05-13  6:44 ` David Mosberger [this message]
2003-05-13 15:42 ` Jes Sorensen
2003-05-13 17:54 ` David Mosberger

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-105590723705749@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --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